From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/commit] Add support for DEC threads on alpha-osf
Date: Tue, 07 Oct 2008 15:02:00 -0000 [thread overview]
Message-ID: <20081007150154.GI28138@adacore.com> (raw)
In-Reply-To: <200810071508.32985.pedro@codesourcery.com>
Thanks for the quick feedback!
> Hmmm, procfs.c. It looks weird that LWP 3 and the main process are
> the same thing. If they are the same, and I haven't messed something up,
> you should only see one of them. IIRC, I don't get that on solaris.
How does it work (to determine whether the process and the LWP are
the same)? I could probably take a look. Not sure whether I could
help much, though.
> ... this is an M:N configuration? It looks like it, because threads
> 2,3,4 were added before the lwps 5,6,7, and the threads 2,3 show a
> different frame from lwps 5,6.
I am strongly suspecting that it is indeed an M:N configuration,
but I don't know that for sure. The LWPs look like kernel threads
(the pthreaddebug API mentions their existence).
> Or, are all user threads scheduled on the main process/lwp ? Then what
> the heck is thread 5 blocked on ? :-)
Very simple: I don't know :). The threads library is a black box
to me. Any other question?
> Anyway, these are all dumb question that came to mind, because
> I miss a description of DEC's thread model at the top of
> dec-thread.c. Something akin to sol-thread.c, but needn't
> be so extensive. :-)
Yes, I miss this description too :). I searched all the headers
as well as the web, and didn't find anything useful. So, my
conclusion at this point is that we can only go with the suspicion
that it is indeed and M:N model. There might be a bug (process
thread should not show up if identical to one of the LWPs),
but this is separate from my patch. I don't mind having a quick
look if it's not too time-consuming. What do you think?
--
Joel
next prev parent reply other threads:[~2008-10-07 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 13:04 Joel Brobecker
2008-10-07 14:08 ` Pedro Alves
2008-10-07 15:02 ` Joel Brobecker [this message]
2008-10-07 15:19 ` Pedro Alves
2008-10-07 15:24 ` Joel Brobecker
2008-10-07 16:36 ` Pedro Alves
2008-10-07 15:21 ` Nathan Froyd
2008-10-20 15:50 ` Joel Brobecker
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=20081007150154.GI28138@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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