From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: gdbarch: ABFD no longer available at gdbarch_update_p time
Date: Thu, 13 Jun 2002 08:14:00 -0000 [thread overview]
Message-ID: <20020613151528.GA4688@nevyn.them.org> (raw)
I'm trying to add a ``set mips abi'' as we discussed earlier. I can't find
a way to do it. The way CRIS does this sort of thing is patently wrong (for
MIPS at least, if not for CRIS also):
/* Update the current architecture, if needed. */
gdbarch_info_init (&info);
if (!gdbarch_update_p (info))
internal_error (__FILE__, __LINE__, "cris_gdbarch_update: failed to update architecture.");
That builds a new architecture based entirely on the defaults. info.abfd is
gone at that point, and that's how MIPS makes lots of its decisions. OSABI
support makes this even more pronounced. I'd like to do:
gdbarch_info_init_current (&info);
but since architectures have an independent lifetime from BFD objects it's
not clear how I can implement that. Thoughts?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2002-06-13 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 8:14 Daniel Jacobowitz [this message]
2002-06-13 9:18 ` Andrew Cagney
2002-06-13 10:50 ` Daniel Jacobowitz
2002-06-13 11:06 ` 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=20020613151528.GA4688@nevyn.them.org \
--to=drow@mvista.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