Date: Thu, 30 Jan 1997 10:43:58 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Luke Steele <luke AT metalworks DOT prestel DOT co DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: SIGSEV error numbers
In-Reply-To: <32ef52e4.266731@news.prestel.co.uk>
Message-ID: <Pine.SUN.3.91.970130103851.17132T-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Wed, 29 Jan 1997, Luke Steele wrote:

> When a djgpp compiled program crashes it usually quotes an error
> number.  Does a list of error codes and their definitions exist?

This question has been asked before, and the answer of the few who know 
how to interpret these error code was that you will need to write a 
treatise on Intel CPUs to explain them.  Since a couple of textbooks 
which explain Intel CPUs exist, though, you might consider getting one of 
them.  Or just post the code here and ask for assistance.

> Also, the contents of eip at the moment of the crash is displayed.  Is
> there an easy way that I can determine the point in my source code
> that the value of eip relates to?

Please read section 9.2 of the DJGPP FAQ list (available as 
v2/faq210b.zip from the same place you get DJGPP).  It describes a small 
wonder called `symify' that's lurking in your djgpp/bin subdirectory, 
which you should use to convert the crash traceback into human-readable 
stack trace, complete with function names, source filenames and line 
numbers, that you can use to pinpoint the problems.