From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D233F3857C5E; Sun, 21 Mar 2021 01:42:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D233F3857C5E From: "phma at bezitopo dot org" To: gdb-prs@sourceware.org Subject: [Bug threads/27618] New: Ignore breakpoints in other threads while debugging one thread Date: Sun, 21 Mar 2021 01:42:37 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 9.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: phma at bezitopo dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Mar 2021 01:42:39 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D27618 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 tripp= ed 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 thr= ough it. Then another thread hit the same breakpoint. I then set scheduler-locki= ng 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 thre= ad, 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 t= he bug. --=20 You are receiving this mail because: You are on the CC list for the bug.=