Re: Access Violation on Application exit

I can't really post the source...it's several thousand lines of code. It
only gives the "Access Violation" upon shut down of the turnkeyed app, not
when run from the console.

As for the BYE, I thought it *had* to be used upon exiting the program. To
clarify, I exit the actual app from a Quit command in a program window, and
then the code goes through the usual DestroyWindow etc. But when the program
has set up the message loops and whatnot, then it exits with a BYE. Without
that the program crashes almost immediately upon execution. If not a BYE,
what is the recommended method of setting up a turnkeyed app?

Bob
***********************************
** Robert Dickow (dickow_at_uidaho.edu) **
** USDA Zone 5 ** Vive le cor!! **
***********************************

----- Original Message -----
From: "Mike Ghan" <mikeghan_at_logix-controls.com>
To: <sftalk_at_forth.com>
Sent: Tuesday, September 18, 2001 2:58 PM
Subject: [sftalk] Re: Access Violation on Application exit

>
> Bob, could you post the relevant source? Does the problem occur when
> the app is turnkeyed or run from the SF console, or both? Typically BYE
> should not be used to exit a turnkeyed program.
>
> Mike
>
> -----Original Message-----
> From: sftalk-bounce_at_forth.com [mailto:sftalk-bounce_at_forth.com]On Behalf
> Of Robert Dickow
> Sent: Tuesday, September 18, 2001 2:18 PM
> To: SF Talk
> Subject: [sftalk] Access Violation on Application exit
>
>
>
> Ok, my Swiftforth app is finished and runs well, with one exception: The
> app
> sends up an error dialog upon quiting the program that says "Access
> Violation". I'm having trouble tracking down this bug, since the program
> runs fine in the Forth console environment. And yes, I do have a BYE at
> the
> end of the application source so that the app runs standalone. The
> program
> worked fine when compiled under SF 2.2.2.
>
> Where should I start looking for this bug? The stack readouts have been
> looking clean in the message loops and callbacks. If this is truly an
> Access
> Violation, wouldn't the program crash at the moment of the attempted
> memory
> access? Maybe this message is not really the problem? Any ideas anybody?
>
> Bob
>
> ***********************************
> ** Robert Dickow (dickow_at_uidaho.edu) **
> ** USDA Zone 5 ** Vive le cor!! **
> ***********************************
>
>
> ----------------------------------------------------------------------
> sftalk_at_forth.com The SwiftForth programming discussion email list
> To unsubscribe, send subject "unsubscribe sftalk" to listar_at_forth.com
> For help with listar commands, send subject "help" to listar_at_forth.com
> Archives are located at http://www.forth.com/sftalk -- check them out!
> Search the archives! Visit http://www.forth.com/search for details.
>

----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe sftalk" to listar_at_forth.com
For help with listar commands, send subject "help" to listar_at_forth.com
Archives are located at http://www.forth.com/sftalk -- check them out!
Search the archives! Visit http://www.forth.com/search for details.
Received on Tue Sep 18 2001 - 15:08:49 PDT