From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CE8F83858D1E; Tue, 29 Nov 2022 19:45:03 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CE8F83858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1669751103; bh=O44vDWxxbBxyfW6vWAWI3UkkGrX9A2yx1s30pBAkcqA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=FVMxykH7LlVy5X73wFFKen+rCEHhkshCLIdMjO71nzstIcAUu7Zi4iAmsNTmx/vSc CCMCfGwHXPGHnIGxiCgB1JYJx9Z/IrlG3rQ6HkRcxwCUo16/OdyjBV+mW4IaPTpXw6 whk8C0tY3+eJBbHADUNTWdoGtaYXirqMxu59M6Bg= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/23251] GDB ignores breakpoint when scheduler-locking is on Date: Tue, 29 Nov 2022 19:45:03 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: WAITING 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: cf_reconfirmed_on everconfirmed bug_status cc Message-ID: In-Reply-To: References: 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 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D23251 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-11-29 Ever confirmed|0 |1 Status|UNCONFIRMED |WAITING CC| |tromey at sourceware dot o= rg --- Comment #1 from Tom Tromey --- It isn't super clear to me what behavior you're expecting. I tried this and I got pretty much the same results. However, here: (gdb) thread 3 [Switching to thread 3 (Thread 0x7ffff6ff0700 (LWP 4036))] #0 sub () at ./if.c:9 9 if(i !=3D 0){ (gdb) c Continuing. [Thread 0x7ffff6ff0700 (LWP 4036) exited] No unwaited-for children left. ... maybe you were expecting a stop at line 10? Unfortunately at this point: (gdb) p i $2 =3D 0 And the reason is that the code does: i =3D 1/i; And since 'i' is an int, this is 0 by this point (since 1/2 =3D=3D 0) I'm putting this into "wait" in case you're still around to clarify what the issue was. --=20 You are receiving this mail because: You are on the CC list for the bug.=