Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: Pedro Alves <palves@redhat.com>,
	Don Breazeal <donb@codesourcery.com>,
	"Breazeal, Don" <Don_Breazeal@mentor.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 3/N] remote follow fork and spurious child stops in non-stop mode
Date: Thu, 30 Jul 2015 18:15:00 -0000	[thread overview]
Message-ID: <55BA69AB.5000005@ericsson.com> (raw)
In-Reply-To: <55BA6959.6070108@redhat.com>

On 15-07-30 02:13 PM, Pedro Alves wrote:
> I think that today I fixed most of the issues this uncovered that I showed
> yesterday, but there's still more to do, so I removed that bit from the
> patch, and pushed it, to both master and 7.10, in order to close PR18600,
> and remove it from the 7.10 blockers list.  Not sure yet whether the
> other new fixes will make it into 7.10.

Thanks a lot for looking into this!


  reply	other threads:[~2015-07-30 18:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 17:24 [PATCH v2 0/2] PR threads/18600: Threads left stopped after fork+thread spawn Pedro Alves
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 [this message]
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=55BA69AB.5000005@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=Don_Breazeal@mentor.com \
    --cc=donb@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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