From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Cedric Le Goater <clg@fr.ibm.com>
Cc: Linux Containers <containers@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: debugging threaded apps running under a clone(CLONE_NEWPID)
Date: Mon, 23 Feb 2009 12:21:53 -0600 [thread overview]
Message-ID: <20090223182153.GD13151@us.ibm.com> (raw)
In-Reply-To: <499EE0D1.1010001@fr.ibm.com>
Quoting Cedric Le Goater (clg@fr.ibm.com):
> Hello !
>
> to debug threaded apps, gdb uses a special libthread_db which seeks in the
> symbols of the exec the list of running threads. This list contains the glibc
> 'struct pthread' descriptor with pids and tids which values are relative
> to the namespace in which the threads were created.
>
> unless you run gdb in the same pid namespace, gdb will not see any thread
> in the debugged app. this is frustrating for some scenarios and some
> support from the kernel would be needed to address this issue. Here
> are some ideas :
>
> . enter a pid namespace. hard.
>
> . expose the pid numbers of a task in its pid namespaces, through some
> ways like /proc/self/stat or /proc/self/pids and modify gdb to make
> the conversion.
>
> How would you do it ?
perhaps a /proc/$$/vpid which prints out
task_pid_nr_ns(tsk, current->nsproxy->pidns)
then each thread opens an fd for /proc/self/vpid and passes it
over an af_unix socket to the parent gdb, which then reads it
to get the pid in its own ns?
-serge
next prev parent reply other threads:[~2009-02-23 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 16:56 debugging threaded apps running under a clone(CLONE_NEWPID) Cedric Le Goater
2009-02-23 18:21 ` Serge E. Hallyn [this message]
[not found] ` <20090223182153.GD13151-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-02-24 9:51 ` Cedric Le Goater
2009-02-24 9:51 ` Cedric Le Goater
2009-02-24 11:28 ` Greg Kurz
2009-02-24 12:09 ` Cedric Le Goater
2009-02-24 14:52 ` Serge E. Hallyn
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=20090223182153.GD13151@us.ibm.com \
--to=serue@us.ibm.com \
--cc=clg@fr.ibm.com \
--cc=containers@lists.osdl.org \
--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.