From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>
Subject: Re: Potential problem between non-stop and linux-thread-db
Date: Tue, 06 Oct 2009 00:49:00 -0000 [thread overview]
Message-ID: <200910060149.26230.pedro@codesourcery.com> (raw)
In-Reply-To: <4ACA9270.3020205@vmware.com>
On Tuesday 06 October 2009 01:42:24, Michael Snyder wrote:
> These were written under the "all-stop" convention, but the comments
> are no longer true, is it not so?
>
> So, async/nonstop guys -- do we need to do anything about this?
AFAIK, these callbacks weren't really used by glibc. Has that
changed recently?
--
Pedro Alves
next prev parent reply other threads:[~2009-10-06 0:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 0:46 Michael Snyder
2009-10-06 0:49 ` Pedro Alves [this message]
2009-10-06 17:34 ` Michael Snyder
2009-10-06 17:44 ` 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=200910060149.26230.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.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