From: Yao Qi <yao@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: don't set the pspace on ordinary breakpoints
Date: Mon, 31 Oct 2011 12:07:00 -0000 [thread overview]
Message-ID: <4EAE6D2C.5010700@codesourcery.com> (raw)
In-Reply-To: <m3lis6h35l.fsf@fleche.redhat.com>
On 10/27/2011 11:20 PM, Tom Tromey wrote:
> First, it changes ordinary breakpoints to set leave their 'pspace' field
> NULL. The rationale for this is that, with the ambiguous linespec
> patch, a linespec may apply to different program spaces, not just the
> one which was selected when the breakpoint was created. For these
> breakpoints, we do not want breakpoint_program_space_exit to remove the
> breakpoint.
>
> @@ -5817,9 +5819,11 @@ init_raw_breakpoint (struct breakpoint *b,
struct gdbarch *gdbarch,
> b->loc->address = adjusted_address;
> b->loc->pspace = sal.pspace;
>
> - /* Store the program space that was used to set the breakpoint, for
> - breakpoint resetting. */
> - b->pspace = sal.pspace;
> + /* Store the program space that was used to set the breakpoint,
> + except for ordinary breakpoints, which are independent of the
> + program space. */
> + if (bptype != bp_breakpoint && bptype != bp_hardware_breakpoint)
> + b->pspace = sal.pspace;
Looks "ordinary breakpoints" includes bp_breakpoint and
bp_hardware_breakpoint. However, as you described above, IIUC,
'ambiguous linespec' should apply to trap tracepoint and fast tracepoint
as well.
--
Yao (é½å°§)
next prev parent reply other threads:[~2011-10-31 9:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 15:32 Tom Tromey
2011-10-31 1:03 ` Jan Kratochvil
2011-10-31 12:07 ` Yao Qi [this message]
2011-11-02 18:55 ` Pedro Alves
2011-11-02 19:47 ` Tom Tromey
2011-11-02 20:21 ` Pedro Alves
2011-11-03 14:01 ` Tom Tromey
2011-11-03 16:02 ` Pedro Alves
2011-11-03 19:33 ` Ulrich Weigand
2011-11-08 19:32 ` Tom Tromey
2011-11-08 20:23 ` Tom Tromey
2011-11-09 18:24 ` Tom Tromey
2011-11-09 18:30 ` Pedro Alves
2011-11-09 18:41 ` Tom Tromey
2011-11-10 16:53 ` Tom Tromey
2011-11-10 17:49 ` Pedro Alves
2011-11-10 17:57 ` Ulrich Weigand
2011-11-10 19:27 ` Tom Tromey
2011-11-10 20:23 ` Tom Tromey
2011-11-11 12:56 ` Ulrich Weigand
2011-11-11 14:47 ` Tom Tromey
2011-11-14 21:12 ` Tom Tromey
2011-11-16 18:37 ` Ulrich Weigand
2011-11-16 21:24 ` Tom Tromey
2011-11-18 18:31 ` Ulrich Weigand
2012-01-02 18:18 ` [7.4 regression] Stand-alone Cell debugging broken (Re: RFC: don't set the pspace on ordinary breakpoints) Ulrich Weigand
2012-01-03 3:15 ` Joel Brobecker
2012-01-03 20:29 ` Tom Tromey
2012-01-04 12:36 ` Ulrich Weigand
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=4EAE6D2C.5010700@codesourcery.com \
--to=yao@codesourcery.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