From: Kumar Gala <kumar.gala@motorola.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: disassembly in gdb?
Date: Thu, 22 May 2003 23:15:00 -0000 [thread overview]
Message-ID: <53C5577E-8CAB-11D7-B5D0-000393DBC2E8@motorola.com> (raw)
In-Reply-To: <1030522225139.ZM31668@localhost.localdomain>
Can you be more specific as to where in i386 or mips that
disassemble_info is set for those targets?
- kumar
On Thursday, May 22, 2003, at 05:51 PM, Kevin Buettner wrote:
> On May 22, 5:24pm, Kumar Gala wrote:
>
>> How does gdb know which disassembler options to use for a given
>> architecture target? For example on PPC there are various flags to
>> enable such things as SPE, AltiVec, ISEL, etc.
>>
>> Is there anyway in an existing gdb to have the disassembler understand
>> a different subset of opcodes for the architecture?
>
> This is supposed to be handled by the disassembler_options field in
> the disassemble_info struct. Unfortunately, I don't see anything
> in the public GDB sources which set these options for any of the
> PPC cores. (mips and i386 have some code which do this though.)
>
> Kevin
next prev parent reply other threads:[~2003-05-22 23:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 14:19 Linux kernel problem -- food for thoughts Elena Zannoni
2003-04-16 14:28 ` Daniel Jacobowitz
2003-04-16 14:38 ` Elena Zannoni
2003-04-16 14:42 ` Daniel Jacobowitz
2003-05-22 22:24 ` disassembly in gdb? Kumar Gala
2003-05-22 22:53 ` Kevin Buettner
2003-05-22 23:15 ` Kumar Gala [this message]
2003-05-22 23:52 ` Kevin Buettner
2003-05-23 15:15 ` Andrew Cagney
2003-04-16 21:04 ` Linux kernel problem -- food for thoughts Roland McGrath
2003-04-16 20:51 ` Roland McGrath
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=53C5577E-8CAB-11D7-B5D0-000393DBC2E8@motorola.com \
--to=kumar.gala@motorola.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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