Charles,

I can't repeat this problem on Window NT4 sp4 . The address you
quote is one of the system DLL's -- which one it is would be defined
entirely by the version of windows you are running. The word .DLL
will show you the starting address of each dll swiftforth has loaded;
from this you can tell which dll caused the error. Then, you can
use DASM to see what the code around the crash area looks like.

This is a bit sneaky, but windows really does load the dlls at the
same addresses each time, and so you can do the little debug bits
while swiftforth is still running...

This is a strange one,

Rick

*********** REPLY SEPARATOR ***********

On 12/3/99 at 7:34 AM SF Talk wrote:

>Date: Fri, 3 Dec 1999 16:14:44 +0100
>From: "Melice" <mail_at_forthcad.com>
>Subject: Help about a (subtle) error ?
>
>
>I'm working on a long program. Since several weeks, I noticed that from
>time to time, the program crash just when exiting.
>
>The error msg is always similar:
>
> "The instruction at '0x77aa446f' referenced memory at '0x0000030'.
> The memory could not be 'read'".
>
>I have checked (as so as possible) the stack and memory usage near the exit
>point: All seems to be OK...
>
>...
>
>Finally, I have today found a sure scenario to reproduce this crash:
>
>With SF1.5 + Notepad or TextPad...
>
>1. in the editor, open any SOURCE.F of THIS program, don't modify the text!
>2. in SwiftForth, include the main source-file, execute main program word.
>3. in the editor modify any text.
>4. quit the program.
>
>Scenari to ALWAYS crash on program exit:
>
> 1 2 3 4
> 2 1 4
>
>But the following NEVER crash:
>
> 1 2 4
> 1 3 2 4
>
>Is there one explanation, or is it an electro-static side-effect ?
>

.
Received on Fri Dec 03 1999 - 08:39:47 PST