Date:	Thu, 21 Jun 2001 14:29:33 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp AT delorie DOT com
Subject:	Re: Strange behavior of compiler.
In-Reply-To:	<3b31a94c.176308036@news.primus.ca>
Message-ID:	<Pine.SUN.3.91.1010621142810.9042M-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 21 Jun 2001 07:58:54 GMT, invalid AT erehwon DOT invalid (Graaagh the
Mighty) sat on a tribble, which squeaked:

>I have more information. On a hunch I looked at the changes. There was
>a bug in one of the debugging bits I added that would in fact have
>jumped into never-never land -- *if* "bar" had ever been reached. So
>why weren't the call frame traceback EIPs more like:
>
>  0x01fc0000   0x1fc0000
>  0x00f00ba7   _bar+42, line 666 of bwlsm.c
>  0x0000178b   _main+275, line 195 of bwlsm.c
>  0x00057b7a   ___crt1_startup+174
>
>even with no aggressive optimizations?

Because the crash happened inside CWSDPMI, and CWSDPMI doesn't have 
access to your program's call stack.

- Raw text -