Date: Sun, 24 Jan 1999 12:11:42 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: djgpp-workers AT delorie DOT com
cc: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Subject: Exceptions in v2.02
Message-ID: <Pine.SUN.3.91.990124120302.11155A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com

I'm consistently observing some very weird phenomena with exceptions and 
signals in v2.02.  For example, when a SIGALRM aborts the program, 
sometimes ES != DS (I even saw SS != DS a couple of times).  In other 
cases, SS:ESP in the traceback point to the exception stack instead of 
the application stack.

Did anybody else see such problems?

Usually these problems happened for me when there were more than a single 
signal that could be raised.  For example, the problems with SIGALRM 
above happened when the program in question was compiled with -pg.

Any ideas?

One problem that particularly bothers me is that I cannot find the place 
in the exception-handling code where we switch back to the normal 
application stack.  Can somebody point my stupid self to the right spot?  
I cannot analyze these problems without knowing where they should have 
been handled.

Thanks in advance.