public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.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	[thread overview]
Message-ID: <bug-23251-4717-utVithcfrn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23251-4717@http.sourceware.org/bugzilla/>

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.

           reply	other threads:[~2022-11-29 19:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-23251-4717@http.sourceware.org/bugzilla/>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-23251-4717-utVithcfrn@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).