From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Debugger
Date:	22 Aug 2000 15:07:54 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	27
Message-ID:	<8nu50a$r55$1@nets3.rz.RWTH-Aachen.DE>
References:	<39A28F2B DOT CD56EEA AT siemens DOT at>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 966956874 27813 137.226.32.75 (22 Aug 2000 15:07:54 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	22 Aug 2000 15:07:54 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Martin Alt <martin DOT alt AT siemens DOT at> wrote:

> What debugger I can use and where do I found it? Is there also a free
> one?

They're all free. At least, I've never heard of any commercial debugger
being able to deal with DJGPP's debug information.

The debuggers we have:

1) gdb  -- the Gnu DeBugger: big, powerful, commandline-oriented

1a) RHIDE -- contains an interface to gdb that feels much like the
             Borland IDE's integrated debuggers do

2) fsdeb -- the FullScreen DEBugger. Look&Feel of Borland's standalone
            TurboDebug. Displays mixed source and assembly

3) edebug32 -- vaguely like classical 'debug'. Essentially stopped being
               actively supported.

You already have fsdeb and edebug32 as part of the djdev*.zip package.
GDB and RHIDE come in their own packages.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -