From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/2] PR threads/18600: Threads left stopped after fork+thread spawn
Date: Thu, 23 Jul 2015 17:24:00 -0000 [thread overview]
Message-ID: <1437672294-29351-1-git-send-email-palves@redhat.com> (raw)
This is intended for both master and 7.10.
The discussions on PR threads/18600 at:
https://sourceware.org/ml/gdb-patches/2015-07/msg00153.html
identified two problems. These patches are another revision of the
patches original posted at:
[1] https://sourceware.org/ml/gdb-patches/2015-07/msg00186.html
[2] https://sourceware.org/ml/gdb-patches/2015-07/msg00190.html
Which later Simon cleaned up a bit and wrote a test for:
https://sourceware.org/ml/gdb-patches/2015-07/msg00595.html
This revision addresses the comments I made to Simon's version.
Tested on x86_64 Fedora 20, native, remote and extended-remote
gdbserver.
Pedro Alves (2):
PR threads/18600: Threads left stopped after fork+thread spawn
PR threads/18600: Inferiors left around after fork+thread spawn
gdb/linux-nat.c | 111 ++++++++++++-----------
gdb/testsuite/gdb.threads/fork-plus-threads.c | 115 ++++++++++++++++++++++++
gdb/testsuite/gdb.threads/fork-plus-threads.exp | 65 ++++++++++++++
3 files changed, 235 insertions(+), 56 deletions(-)
create mode 100644 gdb/testsuite/gdb.threads/fork-plus-threads.c
create mode 100644 gdb/testsuite/gdb.threads/fork-plus-threads.exp
--
1.9.3
next reply other threads:[~2015-07-23 17:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 17:24 Pedro Alves [this message]
2015-07-23 17:25 ` [PATCH v2 1/2] " Pedro Alves
2015-07-30 18:08 ` [pushed] " Pedro Alves
2015-07-23 17:25 ` [PATCH v2 2/2] PR threads/18600: Inferiors left around " Pedro Alves
2015-07-23 18:21 ` [PATCH 3/N] remote follow fork and spurious child stops in non-stop mode Pedro Alves
2015-07-24 18:05 ` Simon Marchi
2015-07-24 18:17 ` Pedro Alves
2015-07-24 18:43 ` Don Breazeal
2015-07-29 13:21 ` Pedro Alves
2015-07-29 13:38 ` Pedro Alves
2015-07-29 14:23 ` Pedro Alves
2015-07-29 15:40 ` Pedro Alves
2015-07-29 16:40 ` Pedro Alves
2015-07-30 18:13 ` Pedro Alves
2015-07-30 18:15 ` Simon Marchi
2015-07-30 21:06 ` Don Breazeal
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=1437672294-29351-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