From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <9604201947.AA11487@clio.rice.edu>
Subject: Re: SQUISHED BUG: symbol name length bug in edebug32 and
To: bill_currie AT MAIL DOT TAIT DOT CO DOT NZ (Bill Currie)
Date: Sat, 20 Apr 1996 14:47:07 -0600 (CDT)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <s17231ec.042@MAIL.TAIT.CO.NZ> from "Bill Currie" at Apr 15, 96 11:24:21 am
Content-Type: text
Content-Length: 967       

> For fsdb, would the following modification be correct
> 
>    else if (i == 8 || (i >= 10 && i <= 14) || i == 17)
>      message (CL_Error, "Exception %d (0x%02x) occurred, error code=%#lx",
>           i, i, a_tss.tss_error);
> |  else if (i < 32)                  /* use to be just 'else' */
>      message (CL_Error, "Exception %d (0x%02x) occurred", i, i);
> 
> This 'fixes' the spurious Exception bug I mentioned earlier, but it would be preferable if I
> could find the real cause of this problem.  I've looked at the exception handling code in
> src/libc/go32 (dpmiexcp.c and exceptn.s) but I couldn't find anything definite.  Is there
> somewhere else I should be looking?

This should NOT be made - we actually have some pseudo exceptions
(hardware interrupts translated to exceptions) with values 0x78 (timer)
0x79 (CTRL-C) and 0x75 (FP errors).  If there are other errors they need
to be fixed, not break the debugger handling of these other exceptions!