public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31440] [gdb] FAIL: gdb.python/py-progspace-events.exp: inferior 1 (timeout) Date: Mon, 04 Mar 2024 09:31:40 +0000 [thread overview] Message-ID: <bug-31440-4717-Yw5Adixjs7@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31440-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31440 --- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> --- I wondered about using print in the python script, and tried this patch, but that doesn't fix it either: ... diff --git a/gdb/testsuite/gdb.python/py-progspace-events.py b/gdb/testsuite/gdb.python/py-progspace-events.py index 23c6fc52f4d..6f41888b65b 100644 --- a/gdb/testsuite/gdb.python/py-progspace-events.py +++ b/gdb/testsuite/gdb.python/py-progspace-events.py @@ -21,11 +21,13 @@ import gdb.events def new_progspace(event): - print("NewProgspaceEvent: %s" % str(event.progspace)) + gdb.write("NewProgspaceEvent: %s\n" % str(event.progspace)) + gdb.flush() def free_progspace(event): - print("FreeProgspaceEvent: %s" % str(event.progspace)) + gdb.write("FreeProgspaceEvent: %s\n" % str(event.progspace)) + gdb.flush() gdb.events.new_progspace.connect(new_progspace) ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-04 9:31 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-02 7:14 [Bug testsuite/31440] New: [gdb/testsuite] " vries at gcc dot gnu.org 2024-03-03 11:40 ` [Bug testsuite/31440] " vries at gcc dot gnu.org 2024-03-04 8:25 ` [Bug gdb/31440] [gdb] " vries at gcc dot gnu.org 2024-03-04 8:58 ` vries at gcc dot gnu.org 2024-03-04 9:31 ` vries at gcc dot gnu.org [this message] 2024-03-04 10:54 ` vries at gcc dot gnu.org 2024-03-04 10:58 ` vries at gcc dot gnu.org 2024-03-04 12:21 ` vries at gcc dot gnu.org
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-31440-4717-Yw5Adixjs7@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: linkBe 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).