From: Simon Farre <simon.farre.cx@gmail.com>
To: gdb-patches@sourceware.org
Cc: Simon Farre <simon.farre.cx@gmail.com>
Subject: [PATCH] Fixes 28ab59607ef40b9571c0702ffba8f6aa6fb1b033
Date: Tue, 20 Jun 2023 20:41:51 +0200 [thread overview]
Message-ID: <20230620184151.288746-1-simon.farre.cx@gmail.com> (raw)
Python formatting errors fixed, introduced by this commit.
---
gdb/testsuite/gdb.python/py-thread-exited.py | 15 ++++++++++++---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/gdb/testsuite/gdb.python/py-thread-exited.py b/gdb/testsuite/gdb.python/py-thread-exited.py
index 32a9e5b01b3..1a55c3dabfb 100644
--- a/gdb/testsuite/gdb.python/py-thread-exited.py
+++ b/gdb/testsuite/gdb.python/py-thread-exited.py
@@ -21,17 +21,25 @@ threadTwoExit = ""
# store it here. we don't care about it though.
mainThreadExit = ""
+
def thread_exited_handler(event):
global threadOneExit, threadTwoExit, mainThreadExit
print("{}".format(event))
assert isinstance(event, gdb.ThreadExitedEvent)
if threadOneExit == "":
- threadOneExit = "event type: thread-exited. global num: {}".format(event.inferior_thread.global_num)
+ threadOneExit = "event type: thread-exited. global num: {}".format(
+ event.inferior_thread.global_num
+ )
else:
if threadTwoExit == "":
- threadTwoExit = "event type: thread-exited. global num: {}".format(event.inferior_thread.global_num)
+ threadTwoExit = "event type: thread-exited. global num: {}".format(
+ event.inferior_thread.global_num
+ )
else:
- mainThreadExit = "event type: thread-exited. global num: {}".format(event.inferior_thread.global_num)
+ mainThreadExit = "event type: thread-exited. global num: {}".format(
+ event.inferior_thread.global_num
+ )
+
class test_events(gdb.Command):
"""Test events."""
@@ -43,4 +51,5 @@ class test_events(gdb.Command):
gdb.events.thread_exited.connect(thread_exited_handler)
print("Event testers registered.")
+
test_events()
--
2.41.0
reply other threads:[~2023-06-20 18:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230620184151.288746-1-simon.farre.cx@gmail.com \
--to=simon.farre.cx@gmail.com \
--cc=gdb-patches@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).