From: Nix <nix@esperi.org.uk>
To: John Clark <jclark@metricsystems.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: GDB, pthreads, and kernel threads
Date: Wed, 18 May 2005 15:01:48 +0100 [thread overview]
Message-ID: <8764xg63ar.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <428A8034.801@metricsystems.com> (John Clark's message of "18 May 2005 00:54:57 +0100")
On 18 May 2005, John Clark announced authoritatively:
> Most of my work has been in the kernel and I had not paid attention to
> user 'threads'. However, I have at the moment to a need to debug a
> user 'pthread' based applicaiton, that I may want to move into the kernel.
>
> However, I can't seem to figure out how to get GDB to debug my user
> pthreads app. What is the correct setup to debug pthreads based applications
> now that it seems that pthreads implementation generates processes/threads
> in the kernel.
Use a recent GDB (>=6.2) and things should just work. (At least, they do
for me.)
--
`End users are just test loads for verifying that the system works, kind of
like resistors in an electrical circuit.' - Kaz Kylheku in c.o.l.d.s
next prev parent reply other threads:[~2005-05-18 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 23:37 GDB, pthreads, and kernel threads John Clark
2005-05-18 14:01 ` Nix [this message]
2005-05-18 15:53 ` John Clark
[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 ` 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
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=8764xg63ar.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--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.