From: Shaun Jackman <sjackman@gmail.com>
To: gdb@sources.redhat.com
Subject: Re: Disassembling ARM and Thumb code
Date: Fri, 06 May 2005 16:35:00 -0000 [thread overview]
Message-ID: <7f45d939050506093578e17a4b@mail.gmail.com> (raw)
In-Reply-To: <20050506040755.GA7038@nevyn.them.org>
On 5/5/05, Daniel Jacobowitz <drow@false.org> wrote:
> > Hehe. I agree, that's probably not the best plan. However, for the
> > unique case of 'x/i $pc' it does make a certain amount of sense to use
> > the CPSR as a hint. I'm not sure if it's worth the special case
> > though. An explicit switch to the x/i and disas commands to specify
> > ARM or Thumb dissection is very much a good idea though.
>
> Yes, probably; if you have a good idea for the syntax to use, then
> maybe we can add it. I don't much like the idea of target-specific
> modifiers.
I like the look of this:
x/i for intelligent
x/iw for ARM
x/ih for Thumb
Another option is...
set disassembly-flavor arm
set disassembly-flavor thumb
Cheers,
Shaun
next prev parent reply other threads:[~2005-05-06 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 0:06 Shaun Jackman
2005-05-06 1:56 ` Daniel Jacobowitz
2005-05-06 3:35 ` Shaun Jackman
2005-05-06 4:08 ` Daniel Jacobowitz
2005-05-06 16:35 ` Shaun Jackman [this message]
2005-05-09 12:48 ` Richard Earnshaw
2005-05-09 16:07 ` Shaun Jackman
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=7f45d939050506093578e17a4b@mail.gmail.com \
--to=sjackman@gmail.com \
--cc=gdb@sources.redhat.com \
/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