From: John Clark <jclark@metricsystems.com>
To: Douglas McNaught <doug@mcnaught.org>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>,
patela@gmail.com
Subject: Re: GDB, pthreads, and kernel threads
Date: Thu, 19 May 2005 10:27:28 -0700 [thread overview]
Message-ID: <428CCC80.1010908@metricsystems.com> (raw)
In-Reply-To: <m21x839n0b.fsf@Douglas-McNaughts-Powerbook.local>
Douglas McNaught wrote:
>John Clark <jclark@metricsystems.com> writes:
>
>
>
>>Also, I do believe I'm using the NPTL package for threads. Is there a
>>way to absolutely tell without
>>question?
>>
>>
>
>If you see multiple 'ps' entries for threads (without using any
>special flags to ps) you are not using NPTL. NPTL is in 2.6 and in
>some vendor 2.4 kernels, but not in kernel.org 2.4.X.
>
>
I used the hint from Ajay Patel and found that in my 'installed' glibc
on my host 'linuxthreads' was being
used. However, I did compile glibc-2.3.5 for the host and results from
that indicate that the nptl threads
version is begin used.
I will see if 1) the Gentoo distribution which was installed on the host
machine I'm using has an updated
version of everything to the nptl threads, or 2) compile gdb against the
glibc-2.3.5 which has the
ntpl threads.
Also, I'm using a 2.6.5 kernel in my host development environment, and
using a 2.6.11.6 kernel
in my target. The target is actually using uClibc, and so I will check
for the type of threads package
that is being supported there as well.
Thanks
John Clark
next prev parent reply other threads:[~2005-05-19 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45k9a-7DD-11@gated-at.bofh.it>
[not found] ` <45xIX-2bR-31@gated-at.bofh.it>
[not found] ` <45zKO-3RV-45@gated-at.bofh.it>
2005-05-19 0:14 ` GDB, pthreads, and kernel threads Robert Hancock
2005-05-19 0:36 ` Ajay Patel
2005-05-19 16:22 ` John Clark
2005-05-19 16:52 ` Douglas McNaught
2005-05-19 17:27 ` John Clark [this message]
2005-05-19 17:02 ` Ajay Patel
2005-05-17 23:37 John Clark
2005-05-18 14:01 ` Nix
2005-05-18 15:53 ` John Clark
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=428CCC80.1010908@metricsystems.com \
--to=jclark@metricsystems.com \
--cc=doug@mcnaught.org \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=patela@gmail.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