Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/3] New Python events.corefile_changed API
Date: Mon, 30 Mar 2026 16:30:50 +0100	[thread overview]
Message-ID: <cover.1774884529.git.aburgess@redhat.com> (raw)

Patch #3 adds a new Python events.corefile_changed registry.

Patches #1 and #2 are some refactoring to make this possible.

Thanks,
Andrew

---

Andrew Burgess (3):
  gdb: delete some unnecessary code from core_target::detach
  gdb: refactor core_target ::close and ::detach functions
  gdb/python: new events.corefile_changed event

 gdb/NEWS                                 |   5 +
 gdb/corelow.c                            |  78 +++++++++----
 gdb/doc/python.texi                      |  11 ++
 gdb/python/py-all-events.def             |   1 +
 gdb/python/py-corefile.c                 |  36 ++++++
 gdb/python/py-event-types.def            |   5 +
 gdb/testsuite/gdb.python/py-corefile.exp | 140 ++++++++++++++++++++---
 gdb/testsuite/gdb.python/py-corefile.py  | 117 +++++++++++++++++++
 8 files changed, 351 insertions(+), 42 deletions(-)


base-commit: 82e460365ba9729e1e66b5f146c17a2ed1b4646c
-- 
2.25.4


             reply	other threads:[~2026-03-30 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 15:30 Andrew Burgess [this message]
2026-03-30 15:30 ` [PATCH 1/3] gdb: delete some unnecessary code from core_target::detach Andrew Burgess
2026-03-30 15:30 ` [PATCH 2/3] gdb: refactor core_target ::close and ::detach functions Andrew Burgess
2026-03-30 15:30 ` [PATCH 3/3] gdb/python: new events.corefile_changed event Andrew Burgess
2026-03-30 17:06   ` Eli Zaretskii

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.1774884529.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