From: Andreas Schwab <schwab@suse.de>
To: Romain Guilleret <rguiller@free.fr>
Cc: gdb@sources.redhat.com
Subject: Re: debugging assembler instructions
Date: Wed, 29 Jan 2003 09:50:00 -0000 [thread overview]
Message-ID: <jewukouvws.fsf@sykes.suse.de> (raw)
In-Reply-To: <20030129081028.GB1976@buffy.herge.org> (Romain Guilleret's message of "Wed, 29 Jan 2003 09:10:28 +0100")
Romain Guilleret <rguiller@free.fr> writes:
|> Hi,
|>
|> I've written assembler code using __asm__. The code does not work as
|> expected and I would like to debug it.
|>
|> Is it possible to do so using GDB ? Ideally, I would like gdb to stop
|> after every assembler instruction so that I can inspect memory or
|> registers to find what's wrong.
|>
|> Is it possible to do so using GDB ?
What's wrong with stepi?
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2003-01-29 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 8:10 Romain Guilleret
2003-01-29 9:50 ` Andreas Schwab [this message]
2003-01-29 11:56 ` Romain Guilleret
2003-01-29 14:52 ` Kris Warkentin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jewukouvws.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb@sources.redhat.com \
--cc=rguiller@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox