This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/19548] breakpoint re-set inserts breakpoints when it shouldn't
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 01 Feb 2016 18:04:21 +0000
- Subject: [Bug breakpoints/19548] breakpoint re-set inserts breakpoints when it shouldn't
- Auto-submitted: auto-generated
- References: <bug-19548-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19548
--- Comment #5 from Pedro Alves <palves at redhat dot com> ---
(Forgot to save this comment before...)
> For some reason, I can't seem to reproduce with 7.10, but I don't understand why.
The difference is that on 7.10, after resetting breakpoint 1, gdb ends up with
inferior_ptid pointing to null_ptid, because when re-setting the breakpoint,
decoding the linespec, gdb finds a sal for the pspace of the inferior that
isn't running, and switches to that pspace, which results in inferior_ptid set
to null_ptid. So afterwards, the breakpoints_should_be_inserted_now call in
update_global_location_list returns false, and insert_breakpoint_locations is
not called.
In master, we don't look at pspaces other than the current so end up never
switching inferior_ptid to null_ptid. And then update_global_location_list
calls insert_breakpoint_locations.
--
You are receiving this mail because:
You are on the CC list for the bug.