From: Tom Tromey <tromey@redhat.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: pedro@codesourcery.com (Pedro Alves),
gdb-patches@sourceware.org,
brobecker@adacore.com (Joel Brobecker)
Subject: Re: RFC: remove gdbarch from struct breakpoint
Date: Tue, 08 Nov 2011 18:10:00 -0000 [thread overview]
Message-ID: <m3ipmuiizd.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201111081718.pA8HInH6022772@d06av02.portsmouth.uk.ibm.com> (Ulrich Weigand's message of "Tue, 8 Nov 2011 18:18:49 +0100 (CET)")
>>>>> "Ulrich" == Ulrich Weigand <uweigand@de.ibm.com> writes:
Ulrich> For example, today we could add a breakpoint like:
Ulrich> break spu.c:123 if var.offset == 123
Ulrich> while currently in PowerPC architecture. The way this was intended
Ulrich> to work is to set a breakpoint location on spu.c:123 (with a location
Ulrich> architecture of "spu"), while evaluating the condition using
Ulrich> PowerPC architecture settings.
Ok.
Ulrich> Well, in the cases I mentioned above (generated code, stack trampolines)
Ulrich> -- which are rare, but possible, breakpoint targets, especially for
Ulrich> single-step breakpoints -- there is no objfile either.
Yeah, I understand now.
Looking back, I am not certain there is an actual need for this patch.
I am going to see what happens if I just drop it.
If I do drop it, I will still pull in the tracepoint changes, since I
think those are probably good.
Tom
next prev parent reply other threads:[~2011-11-08 18:10 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
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 [this message]
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=m3ipmuiizd.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=uweigand@de.ibm.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