From:	aho450s AT nic DOT smsu DOT edu (Tony O'Bryan)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: How does RHIDE debug?
Date:	Fri, 28 Feb 1997 13:06:25 GMT
Organization:	Southwest Missouri State University
Lines:	21
Message-ID:	<3316d725.2925653@ursa.smsu.edu>
References:	<Pine DOT SV4 DOT 3 DOT 94 DOT 970227151621 DOT 10628A-100000 AT aludra DOT usc DOT edu>
NNTP-Posting-Host:	forseti.i107.smsu.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

On 27 Feb 1997 15:24:56 -0800, rellwood <rellwood AT aludra DOT usc DOT edu> 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?

You have to be single-stepping (or at a breakpoint after starting your program
running).  You cannot debug a program without running it.  F8 will single-step
through your code, but will not trace into function calls (it will run function
calls at full speed and place you at the instruction following the called
function), F7 will single-step into function calls (provided the source is
available).  There are others that you will find.  Once the program is actually
executing, all the debug features are unghosted.

>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.

Look in the Debug menu (again, after your program has started).

- Raw text -