From: Daniel Jacobowitz <drow@false.org>
To: Michael Eager <eager@eagercon.com>
Cc: gdb@sources.redhat.com
Subject: Re: Identifying PowerPC architecture
Date: Thu, 11 Jan 2007 20:51:00 -0000 [thread overview]
Message-ID: <20070111205144.GA29057@nevyn.them.org> (raw)
In-Reply-To: <45A6A23F.3000605@eagercon.com>
On Thu, Jan 11, 2007 at 12:46:55PM -0800, Michael Eager wrote:
> I'm looking at how gdb decides which arch/mach it is
> working with for PowerPC. It looks like it always picks up
> rs6000:6000 as processor type.
>
> When rs6000_gdbarch_init(struct gdbarch_info info,
> struct gdbarch_list *arches) is called, arches is NULL.
> As a result, it creates up a default arch/mach based on
> info.bfd_arch_info.
->arches is a list of previously initialized gdbarches. They're
initialized by other calls to rs6000_gdbarch_init.
gdbarch_list_lookup_by_info will only return something with the
same bfd_arch_info as it is passed.
So, if you're not getting the right arch, you're probably not
starting with the right bfd_arch_info. I don't know if PowerPC
tags binaries with the processor; I don't remember any such markings
for PowerPC.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-11 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 20:47 Michael Eager
2007-01-11 20:51 ` Daniel Jacobowitz [this message]
2007-01-11 21:04 ` Michael Eager
2007-01-11 21:22 ` Daniel Jacobowitz
2007-01-11 21:31 ` Mark Kettenis
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=20070111205144.GA29057@nevyn.them.org \
--to=drow@false.org \
--cc=eager@eagercon.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