From: Pedro Alves <palves@redhat.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdbserver: don't pick a random thread if the current thread dies
Date: Mon, 24 Aug 2015 19:09:00 -0000 [thread overview]
Message-ID: <55DB6BD0.8090905@redhat.com> (raw)
In-Reply-To: <20150824183911.4F433124A1@oc7340732750.ibm.com>
On 08/24/2015 07:39 PM, Ulrich Weigand wrote:
> Pedro Alves wrote:
>
>> I've posted the fix now:
>>
>> https://sourceware.org/ml/gdb-patches/2015-08/msg00690.html
>>
>> I've pushed that to the users/palves/gdbserver-crash-without-multiprocess
>> branch, but if you prefer, I'll push it to master instead.
>
> I've tested the branch on Cell/B.E. SPU, both native and via gdbserver.
> Everything looks good again. Please push to master ...
Thanks much for testing. (And sorry for the breakage, of course!)
Now pushed.
--
Pedro Alves
prev parent reply other threads:[~2015-08-24 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 14:54 Pedro Alves
2015-08-21 18:44 ` Pedro Alves
2015-08-24 14:59 ` Ulrich Weigand
2015-08-24 15:30 ` Pedro Alves
2015-08-24 15:47 ` Pedro Alves
2015-08-24 17:02 ` Pedro Alves
2015-08-24 17:08 ` Ulrich Weigand
2015-08-24 17:13 ` Pedro Alves
2015-08-24 18:39 ` Ulrich Weigand
2015-08-24 19:09 ` Pedro Alves [this message]
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=55DB6BD0.8090905@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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