From: Andi Kleen <andi@firstfloor.org>
To: Tom Horsley <tom.horsley@ccur.com>
Cc: linux-kernel@vger.kernel.org, bugsy <bugsy@ccur.com>
Subject: Re: TLS info and core files?
Date: 27 Mar 2007 20:39:38 +0200 [thread overview]
Message-ID: <p738xdi4jkl.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070327092041.40947947@tweety>
Tom Horsley <tom.horsley@ccur.com> writes:
>
> 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.)
I think that would be a good idea. Shouldn't be very hard
to implement. Please send a patch.
We also miss some other information in core files
I found useful in the past, like the CR3 and some other registers.
The printks on x86-64 actually give more information
than a core dump in some cases.
-Andi
prev parent reply other threads:[~2007-03-27 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 13:20 Tom Horsley
2007-03-27 18:39 ` Andi Kleen [this message]
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=p738xdi4jkl.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=bugsy@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.horsley@ccur.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
all inboxes | Powered by JetHome®