From: Pedro Alves <pedro@codesourcery.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Potential problem between non-stop and linux-thread-db
Date: Tue, 06 Oct 2009 17:44:00 -0000 [thread overview]
Message-ID: <200910061844.18580.pedro@codesourcery.com> (raw)
In-Reply-To: <4ACB7ED2.2060803@vmware.com>
On Tuesday 06 October 2009 18:30:58, Michael Snyder wrote:
> Pedro Alves wrote:
> > On Tuesday 06 October 2009 01:42:24, Michael Snyder wrote:
> >
> > AFAIK, these callbacks weren't really used by glibc. Has that
> > changed recently?
>
> Probably not. I was just looking at the code, not actually
> running or debugging it.
Feel free to put a comment there, or let me know if you'd
like me to. In any case, in non-stop mode, at least the current
lwp is always stopped already when we call into thread_db.
It's likely that solaris' thread_db does make use of such
callbacks. I didn't check, but well, they've invented the
interface. We never did merge sol-threads.c and proc-service.c
though, and solaris doesn't support non-stop presently anyway.
--
Pedro Alves
prev parent reply other threads:[~2009-10-06 17:44 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
2009-10-06 17:34 ` Michael Snyder
2009-10-06 17:44 ` 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=200910061844.18580.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