X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
Date:	Fri, 23 Jul 2004 14:07:35 +0200
From:	"Eli Zaretskii" <eliz AT gnu DOT org>
Sender:	halo1 AT zahav DOT net DOT il
To:	djgpp AT delorie DOT com
Message-Id:	<2719-Fri23Jul2004140734+0300-eliz@gnu.org>
X-Mailer:	emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to:	<20040723061522.18203.00000308@mb-m03.aol.com> (sterten@aol.com)
Subject:	Re: strange error
References:	<3405-Fri23Jul2004104057+0300-eliz AT gnu DOT org> <20040723061522 DOT 18203 DOT 00000308 AT mb-m03 DOT aol DOT com>
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

> From: sterten AT aol DOT com (Sterten)
> Newsgroups: comp.os.msdos.djgpp
> Date: 23 Jul 2004 10:15:22 GMT
> 
> sorry, I saw no point in running it through the debugger
> since the error occurred at the end of the program
> after millions of steps.

It doesn't matter how many gazillions of steps it took; running it
under a debugger does not mean you need to single-step it.  Simply run
the program under a debugger without setting any breakpoints, and the
debugger will keep out of the program's way until such time as it
crashes.  Then, and only then, will the debugger kick in, take
control, and let you do things such as disassemblying near the point
of the crash, which will show us what code crashed and why.

This works because the debuggers catches fatal signals of the program
it runs, and a crash is a fatal signal (SIGSEGV in your case).

- Raw text -