From: "Kris Warkentin" <kewarken@qnx.com>
To: "Romain Guilleret" <rguiller@free.fr>, <gdb@sources.redhat.com>
Subject: Re: debugging assembler instructions
Date: Wed, 29 Jan 2003 14:52:00 -0000 [thread overview]
Message-ID: <140e01c2c7a5$f1065310$0202040a@catdog> (raw)
In-Reply-To: <20030129081028.GB1976@buffy.herge.org>
You might want to try:
display /i $pc
and then use stepi. This will show you the instruction you're on as you go.
cheers,
Kris
----- Original Message -----
From: "Romain Guilleret" <rguiller@free.fr>
To: <gdb@sources.redhat.com>
Sent: Wednesday, January 29, 2003 3:10 AM
Subject: debugging assembler instructions
> 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 ?
> If not, does anybody know another tool that could do it ?
>
> I'm using GDB 5.2 on a Debian woody system.
>
> TIA
>
> Romain Guilleret
>
prev parent reply other threads:[~2003-01-29 14:52 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
2003-01-29 11:56 ` Romain Guilleret
2003-01-29 14:52 ` Kris Warkentin [this message]
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='140e01c2c7a5$f1065310$0202040a@catdog' \
--to=kewarken@qnx.com \
--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