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] event loop deadlocks when using continue in breakpoint command and using gdb.execute in stop event hook written in Python
Date: Tue, 11 Apr 2023 22:03:19 +0000	[thread overview]
Message-ID: <bug-29831-4717-k5PtKRjpuL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29831-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29831

--- Comment #1 from Disconnect3d <dominik.b.czarnota+bugzilla at gmail dot com> ---
This can be worked around in the following way. However, this is not a good
solution since this means one can't script GDB using both its native CLI
commands and Python at the same time.

```
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)


class Bp(gdb.Breakpoint):
    def stop(self):
        print("Breakpoint hit!")
        return True

Bp("foo")
```

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-04-11 22:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28  9:00 [Bug gdb/29831] New: event loop deadlocks when using continue in breakpoint command and using gdb.execute in stop event hook dominik.b.czarnota+bugzilla at gmail dot com
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 [this message]
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-k5PtKRjpuL@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).