From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] Exit during detach
Date: Tue, 18 Jul 2023 15:31:44 +0100 [thread overview]
Message-ID: <cover.1689690655.git.aburgess@redhat.com> (raw)
Ran into an issue in non-stop mode where an exit arriving during a
detach would cause GDB to crash.
---
Andrew Burgess (2):
gdb: fix possible nullptr dereference in a remote_debug_printf call
gdb: handle main thread exiting during detach
gdb/linux-nat.c | 19 ++-
gdb/remote.c | 23 ++-
.../main-thread-exit-during-detach.c | 59 ++++++++
.../main-thread-exit-during-detach.exp | 143 ++++++++++++++++++
gdbserver/mem-break.cc | 7 +
5 files changed, 241 insertions(+), 10 deletions(-)
create mode 100644 gdb/testsuite/gdb.threads/main-thread-exit-during-detach.c
create mode 100644 gdb/testsuite/gdb.threads/main-thread-exit-during-detach.exp
base-commit: b26b06dd42fbd9a75eebb4c943bf55a88562b81f
--
2.25.4
next reply other threads:[~2023-07-18 14:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 14:31 Andrew Burgess [this message]
2023-07-18 14:31 ` [PATCH 1/2] gdb: fix possible nullptr dereference in a remote_debug_printf call Andrew Burgess
2023-07-19 15:01 ` Tom Tromey
2023-08-03 9:07 ` Andrew Burgess
2023-07-18 14:31 ` [PATCH 2/2] gdb: handle main thread exiting during detach Andrew Burgess
2023-07-18 14:40 ` Andrew Burgess
2023-08-03 9:50 ` [PATCHv2] " Andrew Burgess
2023-08-23 11:26 ` [PATCHv3] " Andrew Burgess
2023-09-29 13:57 ` [PATCHv4] " Andrew Burgess
2023-10-18 9:49 ` [PATCHv5] " Andrew Burgess
2023-10-25 21:40 ` Kevin Buettner
2023-10-26 17:26 ` 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.1689690655.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).