From:	Nate Eldredge <neldredge AT hmc DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: HELP! : Debugging a c/asm mixed programs
Date:	29 Mar 2000 10:02:44 -0800
Organization:	InterWorld Communications
Lines:	20
Message-ID:	<831z4t3b97.fsf@mercury.st.hmc.edu>
References:	<19464ea8 DOT 15fd37ca AT usw-ex0105-036 DOT remarq DOT com> <8bsuap$j9q$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>
NNTP-Posting-Host:	mercury.st.hmc.edu
Mime-Version:	1.0
X-Trace:	nntp1.interworld.net 954353060 23628 134.173.45.219 (29 Mar 2000 18:04:20 GMT)
X-Complaints-To:	usenet AT nntp1 DOT interworld DOT net
NNTP-Posting-Date:	29 Mar 2000 18:04:20 GMT
User-Agent:	Gnus/5.0802 (Gnus v5.8.2) Emacs/20.5
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

broeker AT physik DOT rwth-aachen DOT de writes:

> batchex <thedark1NOthSPAM AT phreaker DOT net DOT invalid> wrote:

> You should still be able to 'stepi', i.e. single-step in terms of
> assembly operations. GDB won't display any source code, but if you
> 'disassemble' your routine, first, you'll still know where you are.
> You can also 'info reg' to see the register contents. Not very
> convenient, but you can do it.

There are a few tricks for using gdb with assembly.  For instance, you
can use $ with register names; `p $eax' will print the contents of
eax.  Another useful trick is `display /i $pc'; this will make it
disassemble the current instruction whenever you stop, or as you
single-step.  I think these are in the manual somewhere.

-- 

Nate Eldredge
neldredge AT hmc DOT edu

- Raw text -