X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-bounces using -f
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: GDB DEBUGGER INFO???
Date:	7 May 2002 10:31:54 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	40
Message-ID:	<ab8aeq$ej1$1@nets3.rz.RWTH-Aachen.DE>
References:	<WCMB8.475227$f_4 DOT 80879 AT news DOT easynews DOT com>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 1020767514 14945 137.226.32.75 (7 May 2002 10:31:54 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	7 May 2002 10:31:54 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Amministrazione <amministrazione AT eaglegames DOT it> wrote:

> wich is the command in the GDB to see the code in the running??

It's not quite clear what you mean by this.  You can single-step in
GDB (command "step" or just "s"), and it will show the code being
executed, both in terms of C source lines.  You con also single-step
by machine instruction ("stepi" or "si").  This mode won't display the
instruction to be executed, though.

There is no 'slow running' mode like in, say, TurboDebugger, where the
debugger would single-step each CPU instruction, execute it, display
the changes to registers and memory, optionally pause a little while
and go on with the next one, without user interaction.  So you can
"watch" the program run like you would watch TV.

FSDB may be worth checking out --- it may have "slow" mode, but I'm
not sure.

> and hot to use 2 monitors?

You just need to have 2 monitors of the right type, then it's easy.
Unfortunately, the only "right" type for the second screen is an old
Monochrome or "Hercules" card with a suitable monitor attached to it.
If your machine is relatively modern and thus doesn't have any ISA
slots, you're probably out of luck.

DOS can switch back and forth to such a screen using commands 'mode
mono' and 'mode co80'.  OTOH, in a case like this I'd suggest to use
RHIDE's GUI-integrated debugger or its standalone version (rhgdb).
They can be moved to the mono screen and let the application work on
the other.





-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -