Xref:	news2.mv.net comp.os.msdos.djgpp:3973
From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: How do I get a stack trace after a SIGFPE?
Date:	Thu, 16 May 1996 08:47:36 CDT
Organization:	Rice University, Houston, Texas
Lines:	11
Message-ID:	<319b31f8.sandmann@clio.rice.edu>
References:	<199605160119 DOT AA13044 AT interlock DOT wdni DOT com>
Reply-To:	sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host:	clio.rice.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

I can't say for sure, but NT may be delaying you seeing the interrupt, 
or maybe there is a bug in the signal code in this case as far as the
saved register information.  It certainly doesn't look right.  Things
to try:
 1) while in your error catcher routine, look at the values in the
    __djgpp_exception_state structure (sys/exceptn.h ?) and look in
    the source directory src/libc/go32/dpmiexcp.c for hints.
 2) you might try the assembly level floating point store info routine to
    get a copy of the FPU state for examination - I think it contains
    the EIP of the faulting instruction.
Good luck, and let us know what you find.

- Raw text -