public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix threads left stopped after fork+thread spawn (PR threads/18600)
Date: Thu, 23 Jul 2015 11:04:00 -0000	[thread overview]
Message-ID: <55B0CA4D.8040002@redhat.com> (raw)
In-Reply-To: <1437492947-2533-1-git-send-email-simon.marchi@ericsson.com>

On 07/21/2015 04:35 PM, Simon Marchi wrote:
> I am posting the fix suggested by Pedro for bug 18600 [1, 2].  I have to
> admit that I don't fully understand the fix, but it fixes the bug and
> causes no regression according in the testsuite.

Thanks Simon.  I'm playing with this.  I made the test run run against
extended-remote gdbserver, and that caught several issues with
non-stop + the new remote follow-fork support.

Thanks,
Pedro Alves

  reply	other threads:[~2015-07-23 11:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 15:36 Simon Marchi
2015-07-23 11:04 ` Pedro Alves [this message]
2015-07-23 17:10   ` 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=55B0CA4D.8040002@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.com \
    /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).