public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Adding a Python event for when GDB exits
Date: Wed,  8 Sep 2021 14:56:38 +0100	[thread overview]
Message-ID: <cover.1631108877.git.andrew.burgess@embecosm.com> (raw)

Adding a new event for when GDB exits (the second patch).

I ran into some issues with the unrelated inferior exiting event
gdb.ExitedEvent while writing the test for the new GDB exiting event,
which explains the first patch.

Thanks,
Andrew


---

Andrew Burgess (2):
  gdb/python: update events test to handle missing exit_code
  gdb/python: add a new gdb_exiting event

 gdb/NEWS                               |  6 +++
 gdb/doc/python.texi                    | 15 +++++-
 gdb/observable.c                       |  1 +
 gdb/observable.h                       |  4 +-
 gdb/python/py-all-events.def           |  1 +
 gdb/python/py-event-types.def          |  5 ++
 gdb/python/python.c                    | 35 +++++++++++++
 gdb/testsuite/gdb.python/py-events.exp | 69 ++++++++++++++++++++++++++
 gdb/testsuite/gdb.python/py-events.py  | 30 ++++++++++-
 gdb/top.c                              |  6 ++-
 10 files changed, 167 insertions(+), 5 deletions(-)

-- 
2.25.4


             reply	other threads:[~2021-09-08 13:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08 13:56 Andrew Burgess [this message]
2021-09-08 13:56 ` [PATCH 1/2] gdb/python: update events test to handle missing exit_code Andrew Burgess
2021-09-08 14:07   ` Eli Zaretskii
2021-09-23 20:14   ` Tom Tromey
2021-09-08 13:56 ` [PATCH 2/2] gdb/python: add a new gdb_exiting event Andrew Burgess
2021-09-08 14:10   ` Eli Zaretskii
2021-09-24  8:42     ` Andrew Burgess
2021-09-23 20:16   ` Tom Tromey
2021-10-05  9:13 ` [PATCH 0/2] Adding a Python event for when GDB exits Andrew Burgess

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=cover.1631108877.git.andrew.burgess@embecosm.com \
    --to=andrew.burgess@embecosm.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).