From: Tom Horsley <tom.horsley@ccur.com>
To: linux-kernel@vger.kernel.org
Cc: bugsy <bugsy@ccur.com>
Subject: TLS info and core files?
Date: Tue, 27 Mar 2007 09:20:41 -0400 [thread overview]
Message-ID: <20070327092041.40947947@tweety> (raw)
As a debugger developer, I find it quite handy when debugging
a real process to use the PTRACE_GET_THREAD_AREA or
PTRACE_GET_ARCH_PRCTL calls to dig up pthread IDs without
having to know too much about the internals of the pthread
library. (It would be even handier if the info was more
consistent across architectures :-).
In a core file, that information has all disappeared.
Should core files have NOTE entries added for some sort of
thread local storage info to be recorded? (Whatever the
kernel happens to know that won't be accessible anymore
after the process is gone, which would probably vary
from architecture to architecture.)
next reply other threads:[~2007-03-27 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 13:20 Tom Horsley [this message]
2007-03-27 18:39 ` Andi Kleen
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=20070327092041.40947947@tweety \
--to=tom.horsley@ccur.com \
--cc=bugsy@ccur.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®