From: Ajay Patel <patela@gmail.com>
To: John Clark <jclark@metricsystems.com>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: GDB, pthreads, and kernel threads
Date: Thu, 19 May 2005 10:02:27 -0700 [thread overview]
Message-ID: <90f56e480505191002197d3ac@mail.gmail.com> (raw)
In-Reply-To: <428CBD63.8020704@metricsystems.com>
> Also, I do believe I'm using the NPTL package for threads. Is there a
> way to absolutely tell without
> question?
If you run /lib/libc-{version}.so your output will show you what are
you running.
For example:
$/lib/libc-2.3.2.so
GNU C Library stable release version 2.3.2, by Roland McGrath et al.
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 3.2.3 20030502 (Red Hat Linux 3.2.3-20).
Compiled on a Linux 2.4.20 system on 2003-10-02.
Available extensions:
GNU libio by Per Bothner
crypt add-on version 2.1 by Michael Glad and others
linuxthreads-0.10 by Xavier Leroy
-------------------------------->linuxthreads
The C stubs add-on version 2.1.2.
BIND-8.2.3-T5B
NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Glibc-2.0 compatibility add-on by Cristian Gafton
libthread_db work sponsored by Alpha Processor Inc
Thanks
Ajay
next prev parent reply other threads:[~2005-05-19 17:02 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
2005-05-19 17:02 ` Ajay Patel [this message]
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=90f56e480505191002197d3ac@mail.gmail.com \
--to=patela@gmail.com \
--cc=hancockr@shaw.ca \
--cc=jclark@metricsystems.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.