Date: Tue, 13 Jan 1998 10:53:03 +0200 (IST) From: Eli Zaretskii To: Myknees cc: djgpp AT delorie DOT com Subject: Re: debugger and exception, help needed In-Reply-To: <19980113042301.XAA14800@ladder02.news.aol.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Precedence: bulk On 13 Jan 1998, Myknees wrote: > I remember that someone has an interupt list -- Ralph Brown -- is > that how you know how to interpret these values? with an interupt > list? The Interrupt List is too sketchy about this. For starters, it doesn't describe the error codes associated with each exception. I usually find the book "PC Magazine Programmer's Technical Reference: The Processor and Coprocessor" by Robert L. Hummel (Ziff-Davis Press, 1992) be more than enough for understanding exceptions. It has a whole chapter on interrupts and exceptions, which includes detailed descriptions of the causes for each exception and the possible eror codes. > I went to his site, but there it says: > << > 0E INT 0E C - IRQ6 - DISKETTE CONTROLLER > 0E INT 0E C - CPU-generated (80386+ native mode) - PAGE FAULT > 0E INT 0E C - HP 95LX - EXTERNAL CARD INTERRUPT > >> > > How do you know which one is relevant? Exceptions are those marked with "CPU-generated". The others are interrupts (the difference is also explained in the above book). > I am thinking that this stuff help me to understand, for example, the things > that Windows says in the "details" section of the dialog box for a program > error, and also the text that follows a program crash. The info printed by Windows is functionally equivalent to DJGPP's crash traceback.