Date: Sun, 15 Jan 1995 12:26:22 -0500
From: Cuthalion / Sliced Bread <enrico AT max DOT tiac DOT net>
Subject: Re: Unsupported Int?
To: Curtiss Cicco <1CMC3466 AT IBM DOT MTSAC DOT EDU>
Cc: DJGPP Listserver <djgpp AT sun DOT soe DOT clarkson DOT edu>



On Sat, 14 Jan 1995, Curtiss Cicco wrote:

>       Are you by chance, accessing a null pointer instead of the correct
> interrupt? Whenever I see an error message with a 0 in it, the first thi
> ng I check is to see if I'm accessing the null pointer or if it's an arr
> ay that hasn't been initialized.

  Yeah, actually, as happens oh so often, as soon as I posted to this, I 
realized what to do.  I took everything out of the interrupt vector (put 
it in a badly timed, but effective while loop) and let it go.  Since 
interrupts were NOT disabled when this happened, I got a unsupported int 
0x00, and THEN a divide by zero error.  (int 0 is divide by zero.)  But 
now, once in every whole bunch of times when I try to exit, I get an 
unsupported int 0xD.   Oh well.  I'm not going to worry about it unless 
it happens again.  :)