public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
* [Bug threads/27618] New: Ignore breakpoints in other threads while debugging one thread @ 2021-03-21 1:42 phma at bezitopo dot org 2021-03-21 7:28 ` [Bug threads/27618] " schwab@linux-m68k.org ` (2 more replies) 0 siblings, 3 replies; 4+ messages in thread From: phma at bezitopo dot org @ 2021-03-21 1:42 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=27618 Bug ID: 27618 Summary: Ignore breakpoints in other threads while debugging one thread Product: gdb Version: 9.2 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: threads Assignee: unassigned at sourceware dot org Reporter: phma at bezitopo dot org Target Milestone: --- I'd like to ignore breakpoints in other threads once a breakpoint has tripped in one thread. I was debugging a multithreaded program and set a breakpoint in the triop function. One of the threads hit the breakpoint, and I started stepping through it. Then another thread hit the same breakpoint. I then set scheduler-locking so that only one thread would run. triop first locks one triangle, checks whether the triangle should be split, then locks several triangles before splitting the triangle. Unfortunately, another thread was in the middle of the locking routine, so when it tried to lock triangles (the other threads being stopped), it hung. If I could step through a function while other threads could also run the function without tripping the breakpoint and jerking me into the other thread, it would be easier for me to see what the function is doing. I ended up telling the program to use only one worker thread (not a problem timewise, as the file that triggered the bug is tiny) and found and fixed the bug. -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug threads/27618] Ignore breakpoints in other threads while debugging one thread 2021-03-21 1:42 [Bug threads/27618] New: Ignore breakpoints in other threads while debugging one thread phma at bezitopo dot org @ 2021-03-21 7:28 ` schwab@linux-m68k.org 2022-11-29 19:47 ` tromey at sourceware dot org 2022-11-29 20:09 ` tromey at sourceware dot org 2 siblings, 0 replies; 4+ messages in thread From: schwab@linux-m68k.org @ 2021-03-21 7:28 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=27618 --- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> --- You can create a new thread specific breakpoint once you have hit the breakpoint once, disabling the original breakpoint. -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug threads/27618] Ignore breakpoints in other threads while debugging one thread 2021-03-21 1:42 [Bug threads/27618] New: Ignore breakpoints in other threads while debugging one thread phma at bezitopo dot org 2021-03-21 7:28 ` [Bug threads/27618] " schwab@linux-m68k.org @ 2022-11-29 19:47 ` tromey at sourceware dot org 2022-11-29 20:09 ` tromey at sourceware dot org 2 siblings, 0 replies; 4+ messages in thread From: tromey at sourceware dot org @ 2022-11-29 19:47 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=27618 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot org --- Comment #2 from Tom Tromey <tromey at sourceware dot org> --- An oddity of breakpoints is that you can modify the condition but you can't readily modify whether they are thread-specific (and if so which thread). That seems like a nice addition to have. -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug threads/27618] Ignore breakpoints in other threads while debugging one thread 2021-03-21 1:42 [Bug threads/27618] New: Ignore breakpoints in other threads while debugging one thread phma at bezitopo dot org 2021-03-21 7:28 ` [Bug threads/27618] " schwab@linux-m68k.org 2022-11-29 19:47 ` tromey at sourceware dot org @ 2022-11-29 20:09 ` tromey at sourceware dot org 2 siblings, 0 replies; 4+ messages in thread From: tromey at sourceware dot org @ 2022-11-29 20:09 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=27618 --- Comment #3 from Tom Tromey <tromey at sourceware dot org> --- See also bug #9533, which proposes a more generic "modify" command. -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-11-29 20:09 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-03-21 1:42 [Bug threads/27618] New: Ignore breakpoints in other threads while debugging one thread phma at bezitopo dot org 2021-03-21 7:28 ` [Bug threads/27618] " schwab@linux-m68k.org 2022-11-29 19:47 ` tromey at sourceware dot org 2022-11-29 20:09 ` tromey at sourceware dot org
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).