Message-Id:	<m10Vc46-000S7EC@inti.gov.ar>
Comments:	Authenticated sender is <salvador AT natacha DOT inti DOT gov DOT ar>
From:	"Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
Organization:	INTI
To:	"Jared Stevens" <stevja AT caldera DOT com>, djgpp AT delorie DOT com
Date:	Fri, 9 Apr 1999 11:19:31 +0000
MIME-Version:	1.0
Subject:	Re: GDB, or other debuggers
In-reply-to:	<7ejdvc$fk3$1@caldera.com>
X-mailer:	Pegasus Mail for Windows (v2.54)
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Jared Stevens" <stevja AT caldera DOT com> wrote:

> How the heck do I use GDB?

Better choice: with RHIDE.

> If I run a program and it crashes, how do I tell
> which line of code the crash occured on by using the crash info that DJGPP
> supplies you with?

1) Command line:
redirect -e error.txt program.exe
symify -i error.txt -o error.rep program.exe

You'll get the trace back error.rep.

2)  GDB:
gdb program.exe
Run the program (I guess that's the run command, type help or h to get help)
When it crashes use the backtrace (or something like it) command.

3) RHIDE:
Compile your program and run it with Ctrl+F9
When it crashes RHIDE will show you the stack trace in a window and you can 
jump to the code selecting in this window.

I use (3), in some strange cases (2) [under Linux] and (1) only when the 
crash happened in another machine (not mine) and the user sends me the 
information (my editor saves it to disk).

SET
------------------------------------ 0 --------------------------------
Visit my home page: http://welcome.to/SetSoft
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(5411) 4759 0013

- Raw text -