From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10210290040.AA19077@clio.rice.edu>
Subject: Re: GCC 3.2 building with 2.04 trouble on W2K (NTVDM crash)
To: lauras AT softhome DOT net
Date: Mon, 28 Oct 2002 18:40:04 -0600 (CST)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <3133046418.20021028211557@softhome.net> from "Laurynas Biveinis" at Oct 28, 2002 09:15:57 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Maybe an obvious question but does 'put show_call_frame in your own
> wrapper' imply that simply removing 'static' is not good enough?

You need to set the exception state structure; you may be able to do
this with setjmp() - but I don't remember for sure.  An alternate
way would be to only pass the stuff show_call_frame needs and modify
where it accesses exception-state

That's what I ment about a wrapper.  Sorry, out on long business
trips, not much time to do email

> I've tried using this function, but all I get is:
> Call frame traceback EIPs:
>   0x00000000
> Any ideas about this output? Stack corruption? Deep magic somewhere?

The exception state structure isn't set.

> > What service pack are you running?
> 
> SP3 with all pre-SP4 fixes.

I haven't tested vs anything later than SP2, so there is always the 
possibility Microsft broke something.

I downloaded 2.04cvs onto my machine before I left so I could theoretically
try the test if I can get an hour or two free (don't hold your breath,
too many clients to talk to!)  It's win2k sp2