public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dominik.b.czarnota+bugzilla at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29831] New: event loop deadlocks when using continue in breakpoint command and using gdb.execute in stop event hook
Date: Mon, 28 Nov 2022 09:00:11 +0000 [thread overview]
Message-ID: <bug-29831-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29831
Bug ID: 29831
Summary: event loop deadlocks when using continue in breakpoint
command and using gdb.execute in stop event hook
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: dominik.b.czarnota+bugzilla at gmail dot com
Target Milestone: ---
Hi,
There is a case when GDB deadlocks or hang indefinetely when a breakpoint is
hit and:
1) the breakpoint has attached commands and when one of the commands is
`continue`
2) a stop event hook was registered before with a Python script and that hook
executes a `gdb.execute` function
This issue is painful for automating GDB and hits many GDB users that use
plugins written in Python (see [0]). I would appreciate if it is fixed sooner
than later, or, if you can provide any information that may be helpful for
fixing or diagnosing this further.
The bug can be reproduced by doing the following steps:
```
$ echo 'void foo(){}; int main() {foo();}' > example.c && gcc example.c
$ cat gdbs.py
import gdb
def stop_handler (event):
print("Python stop handler started")
print("Thread is stopped: " + str(gdb.selected_thread().is_stopped()))
print("Thread is running: " + str(gdb.selected_thread().is_running()))
(gdb.execute("",to_string=True))
print("Thread is stopped: " + str(gdb.selected_thread().is_stopped()))
print("Thread is running: " + str(gdb.selected_thread().is_running()))
print("Python Stop handler finished\n")
gdb.events.stop.connect (stop_handler)
$ gdb --quiet --nx ./a.out
Reading symbols from ./a.out...
(No debugging symbols found in ./a.out)
(gdb) starti
Starting program: /home/dc/a.out
Program stopped.
0x00007ffff7dd4090 in _start () from /lib64/ld-linux-x86-64.so.2
(gdb) break foo
Breakpoint 1 at 0x5555555545fe
(gdb) commands
Type commands for breakpoint(s) 1, one per line.
End with a line saying just "end".
>continue
>end
(gdb) source gdbs.py
(gdb) c
Continuing.
Breakpoint 1, 0x00005555555545fe in foo ()
Python stop handler started
Thread is stopped: True
Thread is running: False
Thread is stopped: False
Thread is running: True
Python Stop handler finished
```
I was able to reproduce this bug with the following GDB versions:
- 10.2-0ubuntu1~18.04~2
- 12.1 compiled from sources (../configure && make -j)
[0] https://github.com/pwndbg/pwndbg/issues/425
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-11-28 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 9:00 dominik.b.czarnota+bugzilla at gmail dot com [this message]
2022-11-28 9:00 ` [Bug gdb/29831] event loop deadlocks when using continue in breakpoint command and using gdb.execute in stop event hook written in Python dominik.b.czarnota+bugzilla at gmail dot com
2023-04-11 22:03 ` dominik.b.czarnota+bugzilla at gmail dot com
2023-04-12 2:47 ` simark at simark dot ca
2023-04-12 21:30 ` aburgess at redhat dot com
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-29831-4717@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).