From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: remove gdbarch from struct breakpoint
Date: Mon, 07 Nov 2011 15:21:00 -0000 [thread overview]
Message-ID: <20111107152058.GD14508@adacore.com> (raw)
In-Reply-To: <m3pqhih3ke.fsf@fleche.redhat.com>
> This patch removes the 'gdbarch' field from struct breakpoint.
>
> In most cases, it is sufficient to replace the use of this field with
> the location's gdbarch instead. In fact, I think the cases in
> tracepoint.c where this is not done are probably latent bugs.
I think that makes sense. I am trying to figure out how a breakpoint
could have a gdbarch that made some sort of sense when the breakpoint
has two locations and each location had a different gdbarch from
the other....
--
Joel
next prev parent reply other threads:[~2011-11-07 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 15:21 Tom Tromey
2011-11-07 15:21 ` Joel Brobecker [this message]
2011-11-07 16:10 ` Pedro Alves
2011-11-07 16:52 ` Stan Shebs
2011-11-08 16:22 ` Ulrich Weigand
2011-11-08 17:00 ` Tom Tromey
2011-11-08 17:19 ` Ulrich Weigand
2011-11-08 18:10 ` Tom Tromey
2011-11-09 18:22 ` Tom Tromey
2011-11-14 16:10 ` FYI: tracepoints and multi-arch (Was: RFC: remove gdbarch from struct breakpoint) Tom Tromey
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=20111107152058.GD14508@adacore.com \
--to=brobecker@adacore.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