Mail Archives: djgpp/1997/02/27/19:21:35
From: | rellwood <rellwood AT aludra DOT usc DOT edu>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | How does RHIDE debug?
|
Date: | 27 Feb 1997 15:24:56 -0800
|
Organization: | University of Southern California, Los Angeles, CA
|
Lines: | 13
|
Sender: | rellwood AT aludra DOT usc DOT edu
|
Message-ID: | <Pine.SV4.3.94.970227151621.10628A-100000@aludra.usc.edu>
|
NNTP-Posting-Host: | aludra.usc.edu
|
Mime-Version: | 1.0
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
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,
Richard
- Raw text -