Mail Archives: djgpp/1997/10/13/22:14:23
Date: | Mon, 13 Oct 1997 19:13:21 -0700 (PDT)
|
Message-Id: | <199710140213.TAA29148@adit.ap.net>
|
Mime-Version: | 1.0
|
To: | djgpp AT delorie DOT com
|
From: | Nate Eldredge <eldredge AT ap DOT net>
|
Subject: | Re: wanted: recommendation for a good debugger
|
At 12:31 10/10/1997 GMT, Newbie wrote:
>I'm just starting using rhide 1.4. Maybe it's just my inexperience, but I
>found rhide's built-in debugger to be somewhat buggy, often times codes are
>not shown properly.
>
>I wonder if anyone can suggest a good debugger?
The only other DJGPP source-level debugger is GDB. But RHIDE's debugger is
based on it, and uses the same internals, so that may not be much better.
Plus, most people consider the interface (command-line) leaves something to
be desired compared to RHIDE. There are fsdb and edebug, but they aren't
source level and will only show you a disassembly of your code.
If you have found bugs in RHIDE, please report them. If they can get fixed,
you'll have a better debugger and so will everyone else.
Nate Eldredge
eldredge AT ap DOT net
- Raw text -