From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PUSHED] gdb/python: reformat file with black
Date: Mon, 2 Oct 2023 21:11:10 +0100 [thread overview]
Message-ID: <e030ce2c79feee6a35665a6580a23dcf937ea46f.1696277448.git.aburgess@redhat.com> (raw)
In-Reply-To: <72cbc08125523c408306fca80317b9e7fad6e82e.1695993752.git.aburgess@redhat.com>
Reformat a Python file with black after this commit:
commit 59912fb2d22f8a4bb0862487f12a5cc65b6a013f
Date: Tue Sep 19 11:45:36 2023 +0100
gdb: add Python events for program space addition and removal
There should be no functional change with this commit.
---
gdb/testsuite/gdb.python/py-progspace-events.py | 3 +++
1 file changed, 3 insertions(+)
diff --git a/gdb/testsuite/gdb.python/py-progspace-events.py b/gdb/testsuite/gdb.python/py-progspace-events.py
index 3abb421cffa..555221dcd4e 100644
--- a/gdb/testsuite/gdb.python/py-progspace-events.py
+++ b/gdb/testsuite/gdb.python/py-progspace-events.py
@@ -19,11 +19,14 @@
import gdb
import gdb.events
+
def new_progspace(event):
print("NewProgspaceEvent: %s" % str(event.progspace))
+
def free_progspace(event):
print("FreeProgspaceEvent: %s" % str(event.progspace))
+
gdb.events.new_progspace.connect(new_progspace)
gdb.events.free_progspace.connect(free_progspace)
base-commit: 57c699398c1a61f1a57574a5ed64654cbadd2a50
--
2.25.4
prev parent reply other threads:[~2023-10-02 20:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 12:44 [PATCH] gdb: add Python events for program space addition and removal Andrew Burgess
2023-09-21 19:20 ` Tom Tromey
2023-09-27 10:51 ` Andrew Burgess
2023-09-27 14:20 ` Tom Tromey
2023-09-27 15:17 ` Andrew Burgess
2023-09-27 15:16 ` [PATCHv2] " Andrew Burgess
2023-09-29 12:41 ` Eli Zaretskii
2023-09-29 13:24 ` [PATCHv3] " Andrew Burgess
2023-09-29 15:46 ` Eli Zaretskii
2023-10-02 16:09 ` Andrew Burgess
2023-10-02 18:34 ` Simon Marchi
2023-10-02 20:36 ` Andrew Burgess
2023-10-02 20:38 ` Simon Marchi
2023-10-02 21:17 ` Andrew Burgess
2023-10-02 20:11 ` Andrew Burgess [this message]
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=e030ce2c79feee6a35665a6580a23dcf937ea46f.1696277448.git.aburgess@redhat.com \
--to=aburgess@redhat.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).