From: Alexandre Oliva <aoliva@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: use MIPS NewABI register names when disassembling NewABI code
Date: Tue, 08 Apr 2003 11:59:00 -0000 [thread overview]
Message-ID: <oru1d9ci9a.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <3E927BCA.1080702@redhat.com>
On Apr 8, 2003, Andrew Cagney <ac131313@redhat.com> wrote:
> Ugly? This bit:
>> + static asymbol *symbols = NULL;
> is wrong. There is more than one instance of an architecture.
Uh. I see. So much for trying to get rid of one more call to
bfd_alloc. This is easy to fix, though.
> How does objdump manage to correctly disassemble something like an
> srecord?
Presumably, it doesn't. If it's not an ELF bfd, it has no way to tell
which ABI to disassemble for.
> GDB should be using that same mechanism.
That's exactly what I'm trying to do :-)
Is there any chance of getting this in after fixing the memory
allocation issue, or must I try to introduce some means for the caller
to specify which ABI to disassemble for?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2003-04-08 11:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 2:31 Alexandre Oliva
2003-04-08 7:35 ` Andrew Cagney
2003-04-08 11:59 ` Alexandre Oliva [this message]
2003-04-08 21:03 ` Andrew Cagney
2003-04-09 3:45 ` Alexandre Oliva
2003-04-09 13:57 ` Daniel Jacobowitz
2003-04-09 14:52 ` Andrew Cagney
2003-04-11 5:43 ` Alexandre Oliva
[not found] ` <mailpost.1050039798.9718@news-sj1-1>
2003-04-11 6:03 ` cgd
2003-04-11 7:47 ` Alexandre Oliva
2003-04-11 15:06 ` Andrew Cagney
2003-04-12 0:31 ` Alexandre Oliva
2003-04-28 21:13 ` Andrew Cagney
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=oru1d9ci9a.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@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