From: Pedro Alves <pedro@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix internal-error on dead LWPs with no associated thread
Date: Mon, 29 Jun 2009 18:30:00 -0000 [thread overview]
Message-ID: <200906291931.22369.pedro@codesourcery.com> (raw)
In-Reply-To: <20090629174929.GA9652@host0.dyn.jankratochvil.net>
On Monday 29 June 2009 18:49:29, Jan Kratochvil wrote:
> Your patch works for my testcase and I failed to find any countercase for it.
> It has no regressions on {x86_64,i686}-fedora-linux-gnu.
Thanks for testing.
> Could you please check it in?
Done. We're now a bit closer to always context-switching
to the event thread in all-stop too. :-) Everytime we don't,
it's most likely a bug waiting to happen.
> Also the attached testcase needs an approval.
Approved.
--
Pedro Alves
next prev parent reply other threads:[~2009-06-29 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 10:09 Jan Kratochvil
2009-06-29 10:35 ` Pedro Alves
2009-06-29 17:51 ` Jan Kratochvil
2009-06-29 18:30 ` Pedro Alves [this message]
2009-06-29 18:59 ` Jan Kratochvil
2009-06-29 18:31 ` Jan Kratochvil
2009-06-29 18:41 ` Pedro Alves
2009-06-29 21:35 ` Jan Kratochvil
2009-06-29 21:42 ` Pedro Alves
2009-06-29 21:48 ` Jan Kratochvil
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=200906291931.22369.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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