From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: should deprecated_target_gdbarch_select_hack be un-deprecated?
Date: Fri, 09 Nov 2012 19:40:00 -0000 [thread overview]
Message-ID: <509D5C1F.2010507@redhat.com> (raw)
In-Reply-To: <877gpuegsb.fsf@fleche.redhat.com>
On 11/09/2012 07:07 PM, Tom Tromey wrote:
>
> Finally, I wonder whether deprecated_target_gdbarch_select_hack should
> be un-deprecated. The comment says:
>
> /* Helper function. Set the global "target_gdbarch" to "gdbarch".
>
> FIXME: kettenis/20031124: Of the functions that follow, only
> gdbarch_from_bfd is supposed to survive. The others will
> dissappear since in the future GDB will (hopefully) be truly
> multi-arch. However, for now we're still stuck with the concept of
> a single active architecture. */
>
> It seems to me that we have settled on a somewhat different design; but
> also that the badness indicated by this comment no longer exists.
Yes, I think so. We used to do nasty things with swapping out gdbarch's
fields, which I believe would be the gross "hack" part, but that is gone.
--
Pedro Alves
next prev parent reply other threads:[~2012-11-09 19:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 1:52 [PATCH] Multi-process + multi-arch: GDB Pedro Alves
2012-11-09 5:26 ` H.J. Lu
2012-11-09 10:07 ` Pedro Alves
2012-11-09 18:24 ` Tom Tromey
2012-11-09 18:30 ` Pedro Alves
2012-11-09 18:32 ` Tom Tromey
2012-11-09 18:47 ` Pedro Alves
2012-11-09 19:08 ` Tom Tromey
2012-11-09 19:14 ` Pedro Alves
2012-11-09 19:18 ` Tom Tromey
2012-11-09 19:40 ` Pedro Alves [this message]
2012-11-13 21:17 ` should deprecated_target_gdbarch_select_hack be un-deprecated? Tom Tromey
2012-11-14 13:54 ` Pedro Alves
2012-11-14 15:34 ` Tom Tromey
2012-11-10 16:25 ` [PATCH] Multi-process + multi-arch: GDB Michael Eager
2012-11-13 20:50 ` Tom Tromey
2012-11-14 13:48 ` Pedro Alves
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=509D5C1F.2010507@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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