Date:	Sun, 21 Jan 2001 11:21:46 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Florian X <dos DOT fire AT aon DOT at>
cc:	djgpp AT delorie DOT com
Subject:	Re: silly question: SIGSEGV
In-Reply-To:	<3a6aa0ac$0$20144@SSP1NO25.highway.telekom.at>
Message-ID:	<Pine.SUN.3.91.1010121111642.13920S-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 21 Jan 2001, Florian X wrote:

> The problem is, that I couldn't find the bug. symify, rhgdb etc. tells me in
> which funktions it shut's down, but not much more (with the DLX library it
> is much difficulter).

Do you mean to say that this bug only shows up if you use DLX, and that 
using DLX somehow invalidates the EIP values printed in the crash message?

Can you run the program under a debugger?  If so, then both GDB and RHIDE 
should be able to tell you a lot about each EIP value printed in the 
crash message.  Perhaps you didn't use the right commands.

> So I don't know, how to continue search it :(

You _must_ find the place in the source code where it crashes.  There's 
no other way.

If nothing else helps, you could selectively remove parts of the code in 
the approximate area where it crashes, until you arrive at a single line 
or maybe a small number of lines whose removal causes the crashes to 
appear.

> Other people have no problem with this program, some has also.....why??

Memory-related bugs are usually like that.

- Raw text -