Date: Mon, 15 Nov 1999 11:44:01 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: The Advisor <TheAdvisor AT cadvision DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: SIGSEGV - oh how we love you
In-Reply-To: <382f6cb9@news.cadvision.com>
Message-ID: <Pine.SUN.3.91.991115114310.26969O-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 14 Nov 1999, The Advisor wrote:

> Wow! just when you think you've got it all figured out... out pops another
> SIGSEGV.. I guess the problem still lies somewhere....

A suggestion: stop randomly poking around, be methodical.  Right now,
as far as I can tell, you don't even know exactly where does the
program crash.

Run SYMIFY on the crash message (see section 9.2 of the DJGPP FAQ, if
you don't know what SYMIFY is).  Look at the information it produces:
it will pinpoint the place in your code where the crash happens.  Take
a good look at that code fragment and try to figure out what's wrong
with it.  If that doesn't help, run the program under a debugger and
see what goes wrong and why.

Also, the crash message is there for a reason, you should examine it
more carefully.  Section 12.2 of the FAQ explains how to read the
crash message and how to begin debugging your program using the
information it presents.