From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v3 0/7] glibc-2.34: Fix gdb.base/gdb-sigterm.exp failure/error
Date: Sat, 26 Feb 2022 17:00:44 -0700 [thread overview]
Message-ID: <20220227000051.3336149-1-kevinb@redhat.com> (raw)
This series addresses Pedro's concerns regarding the v2 series posted
last year:
https://sourceware.org/pipermail/gdb-patches/2021-August/181575.html
In particular, it introduces a new exception which will be thrown
when GDB receives a SIGTERM. That exception is handled at the
top level when possible, though for the extension languages, Python
and Guile, a somewhat different approach had to be taken. In order to
ensure that this new exception isn't inadvertently swallowed on its
way up to the top level, I also did an audit of the try / catch code
involving gdb_exception, making adjustments where necessary.
Kevin Buettner (7):
Introduce gdb_exception_forced_quit
Handle gdb SIGTERM by throwing / catching gdb_exception_force_quit
Catch gdb_exception_error instead of gdb_exception (in many places)
Python QUIT processing updates
Guile QUIT processing updates
QUIT processing w/ explicit throw for gdb_exception_forced_quit
Handle QUIT processing in the scoped_switch_fork_info destructor
gdb/ada-lang.c | 2 +-
gdb/breakpoint.c | 8 ++++----
gdb/cli/cli-interp.c | 2 +-
gdb/event-top.c | 2 ++
gdb/guile/guile-internal.h | 5 +++++
gdb/guile/scm-pretty-print.c | 5 +++++
gdb/guile/scm-type.c | 5 +++++
gdb/guile/scm-value.c | 5 +++++
gdb/i386-linux-tdep.c | 2 +-
gdb/inf-loop.c | 2 +-
gdb/infcmd.c | 2 +-
gdb/infrun.c | 2 +-
gdb/jit.c | 2 +-
gdb/linux-fork.c | 13 +++++++++++++
gdb/main.c | 12 ++++++++++++
gdb/mi/mi-cmd-break.c | 2 +-
gdb/mi/mi-interp.c | 2 +-
gdb/mi/mi-main.c | 4 ++++
gdb/objc-lang.c | 2 +-
gdb/parse.c | 2 +-
gdb/printcmd.c | 2 +-
gdb/python/py-finishbreakpoint.c | 5 +++++
gdb/python/py-gdb-readline.c | 4 ++++
gdb/python/py-symbol.c | 5 +++++
gdb/python/py-utils.c | 3 +++
gdb/python/py-value.c | 5 +++++
gdb/record-btrace.c | 2 +-
gdb/record-full.c | 2 +-
gdb/remote-fileio.c | 15 ++++++++++-----
gdb/solib.c | 2 +-
gdb/sparc64-linux-tdep.c | 2 +-
gdb/symfile-mem.c | 2 +-
gdb/top.h | 2 +-
gdb/tui/tui-io.c | 4 ++++
gdb/tui/tui.c | 4 ++++
gdb/utils.c | 2 +-
gdb/windows-nat.c | 4 ++++
gdbsupport/common-exceptions.cc | 14 ++++++++++++++
gdbsupport/common-exceptions.h | 22 +++++++++++++++++++++-
39 files changed, 153 insertions(+), 29 deletions(-)
--
2.35.1
next reply other threads:[~2022-02-27 0:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 0:00 Kevin Buettner [this message]
2022-02-27 0:00 ` [PATCH v3 1/7] Introduce gdb_exception_forced_quit Kevin Buettner
2022-02-27 0:00 ` [PATCH v3 2/7] Handle gdb SIGTERM by throwing / catching gdb_exception_force_quit Kevin Buettner
2022-02-27 0:00 ` [PATCH v3 3/7] Catch gdb_exception_error instead of gdb_exception (in many places) Kevin Buettner
2022-03-03 21:11 ` Pedro Alves
2022-02-27 0:00 ` [PATCH v3 4/7] Python QUIT processing updates Kevin Buettner
2022-02-27 0:00 ` [PATCH v3 5/7] Guile " Kevin Buettner
2022-02-27 0:00 ` [PATCH v3 6/7] QUIT processing w/ explicit throw for gdb_exception_forced_quit Kevin Buettner
2022-03-03 21:26 ` Pedro Alves
2022-02-27 0:00 ` [PATCH v3 7/7] Handle QUIT processing in the scoped_switch_fork_info destructor Kevin Buettner
2022-07-20 1:53 ` [PATCH v3 0/7] glibc-2.34: Fix gdb.base/gdb-sigterm.exp failure/error Simon Marchi
2023-01-05 13:35 ` Tom de Vries
2023-01-10 15:19 ` Pedro Alves
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=20220227000051.3336149-1-kevinb@redhat.com \
--to=kevinb@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).