From:	Ian Chapman <ichapman AT nortel DOT ca>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: How does RHIDE debug?
Date:	Thu, 27 Feb 1997 22:03:05 -0800
Organization:	Bell Northern Research
Lines:	23
Message-ID:	<33167519.58E2@nortel.ca>
References:	<Pine DOT SV4 DOT 3 DOT 94 DOT 970227151621 DOT 10628A-100000 AT aludra DOT usc DOT edu>
NNTP-Posting-Host:	amert421.bnr.ca
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

rellwood wrote:
> 
> I can see that RHIDE comes with some program tracing options in the Run
> menu, but how do I use these?  They seem to be ghosted all the time, even
> when I turn on the -g option, which I thought would fix it.  What am I
> missing?
> 
> Also, does RHIDE have any sort of feature similar to WATCHES or INSPECTORS
> as Turbo C++ does?  In Turbo C++'s IDE these are awesome, and it would be
> irritating if I had to shell out to GDB in order to inspect my variables,
> classes, etc.
> 
> Thanks,
> RichardRichard,
     I've used gdb I think it stands for gnu debug.  There are .zip files with all 
the stuff in them to make it go.  I managed to trace a bug in a c program that I'd 
ported from another compiler.  gdb did the job but once I set a watch on a data 
value it was like waiting to die.  Mind you I'm only a beginner there are faster 
ways to home in once you find your feet I'm sure.  Your shaddowed selections may 
be because you have not installed the app that they call.  Are you sure that you 
have all the .zips that you need.

           Regards Ian.

- Raw text -