public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/23251] GDB ignores breakpoint when scheduler-locking is on
[not found] <bug-23251-4717@http.sourceware.org/bugzilla/>
@ 2022-11-29 19:45 ` tromey at sourceware dot org
0 siblings, 0 replies; only message in thread
From: tromey at sourceware dot org @ 2022-11-29 19:45 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=23251
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-11-29
Ever confirmed|0 |1
Status|UNCONFIRMED |WAITING
CC| |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
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 != 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 = 0
And the reason is that the code does:
i = 1/i;
And since 'i' is an int, this is 0 by this point (since 1/2 == 0)
I'm putting this into "wait" in case you're still around to clarify
what the issue was.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-11-29 19:45 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-23251-4717@http.sourceware.org/bugzilla/>
2022-11-29 19:45 ` [Bug gdb/23251] GDB ignores breakpoint when scheduler-locking is on 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).