From: Andrew Cagney <ac131313@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfc] Swap out current when creating a new architecture
Date: Sun, 30 Sep 2001 12:25:00 -0000 [thread overview]
Message-ID: <3BB771A1.4070201@cygnus.com> (raw)
In-Reply-To: <3BB16441.30805@cygnus.com>
> The attached changes the run-time environment within which a new architectures are created. Briefly the simplified sequence:
>
> - call XXX_gdbarch_init()
> - swap out old architecture
> - install new architecture
>
> is changed to:
>
> - swap out old architecture
> - call XX_gdbarch_init()
> - install new architecture
>
> This has the effect of making current_gdbarch invalid for the lifetime of the XXX_gdbarch_init() call.
>
This patch is evi^D^D^D nasty.
The CRIS target also dumps core with it applied. Like rs6000 was, it is
refering to the previous (current_gdbarch) architecture.
I'll sit on this for a bit longer. Could I encourage target maintainers
to check their XXX_gdbarch_init() function for references to
current_gdbarch.
Andrew
next prev parent reply other threads:[~2001-09-30 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BB16441.30805@cygnus.com>
2001-09-26 22:56 ` Kevin Buettner
2001-09-26 23:06 ` Andrew Cagney
2001-09-30 12:25 ` Andrew Cagney [this message]
2001-10-01 4:34 ` Orjan Friberg
2001-10-14 17:07 ` Andrew Cagney
2001-10-15 18:41 ` Andrew Cagney
2001-10-16 1:59 ` Orjan Friberg
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=3BB771A1.4070201@cygnus.com \
--to=ac131313@cygnus.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