From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Fix gdbserver crash on all non-GNU/Linux targets
Date: Mon, 24 Aug 2015 17:10:00 -0000 [thread overview]
Message-ID: <1440436237-24015-1-git-send-email-palves@redhat.com> (raw)
Documentation review needed on patch #1.
This series fixes the crash Ulrich reported here:
https://sourceware.org/ml/gdb-patches/2015-08/msg00675.html
In order to add a test that exposes the issue on GNU/Linux, I need to
add the missing "set remote ...-packet" knob to disable the
multiprocess extensions.
I've pushed this to the
users/palves/gdbserver-crash-without-multiprocess branch for testing
convenience.
Pedro Alves (2):
Add "set remote multiprocess-extensions-packet" command
gdbserver crashes when multiprocess extensions aren't supported
gdb/NEWS | 4 ++
gdb/doc/gdb.texinfo | 4 ++
gdb/gdbserver/inferiors.c | 8 +++
gdb/gdbserver/inferiors.h | 3 +
gdb/gdbserver/remote-utils.c | 7 ++-
gdb/remote.c | 7 ++-
.../gdb.server/connect-without-multi-process.c | 22 +++++++
.../gdb.server/connect-without-multi-process.exp | 68 ++++++++++++++++++++++
8 files changed, 118 insertions(+), 5 deletions(-)
create mode 100644 gdb/testsuite/gdb.server/connect-without-multi-process.c
create mode 100644 gdb/testsuite/gdb.server/connect-without-multi-process.exp
--
1.9.3
next reply other threads:[~2015-08-24 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 17:10 Pedro Alves [this message]
2015-08-24 17:10 ` [PATCH 2/2] gdbserver crashes when multiprocess extensions aren't supported Pedro Alves
2015-08-24 17:10 ` [PATCH 1/2] Add "set remote multiprocess-extensions-packet" command Pedro Alves
2015-08-24 17:28 ` Eli Zaretskii
2015-08-24 17:31 ` Pedro Alves
2015-08-24 17:34 ` 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=1440436237-24015-1-git-send-email-palves@redhat.com \
--to=palves@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