Message-Id: <199710140007.KAA15635@rabble.uow.edu.au>
Subject: Re: wanted: recommendation for a good debugger
To: new AT no_spam DOT com (Newbie)
Date: Tue, 14 Oct 1997 10:07:35 +1000 (EST)
Cc: djgpp AT delorie DOT com (DJGPP)
In-Reply-To: <01bcd578$65320520$180867d1@default> from Newbie at "Oct 10, 97 12:31:55 pm"
From: Brett Porter <bporter AT rabble DOT uow DOT edu DOT au>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

> 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?
> 
Buggy? What do you mean when you say the codes are not shown properly?

I found it great to use, especially coming from a Turbo Debugger background.

Alternatives?

Well there is GDB, but it is a text-based command line driven debugger.
Apparently it can do more than RHGDB (the debugger built in to RHIDE), but
I've found it is thousands of times harder to learn and use (but like I
said, I've been spoilt by Turbo Debugger and the Borland IDE for too many years)

There is also FSDB but it is assembly only, and fairly limited. Obsolete
since RHIDE got a disassembler, as far as I'm concerned.

I haven't used the MSDOS version of EMacs, but I'm sure it would have some
sort of debugging capability.

Brett

-- 
"Give me ambiguity or give me something else"
--
Brett Porter
bporter AT rabble DOT uow DOT edu DOT au

http://www.geocities.com/CollegePark/Union/3596
	Humour, Programming, and more.