From: Tom Horsley <tom.horsley@ccur.com>
To: <linux-kernel@vger.kernel.org>
Cc: "Horsley, Tom" <Tom.Horsley@ccur.com>
Subject: Re: [PATCH -mm 42/43] x86 core dump TLS
Date: Wed, 20 Oct 2010 10:31:44 -0400 [thread overview]
Message-ID: <20101020103144.673c6bdc@tomh> (raw)
Way back in 2007 this patch started wending its way into the
kernel:
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg242889.html
That adds the NT_386_TLS NOTE segment entries to core files, which
are quite handy for recovering the pthread_self() values for
multiple threads in a core file from a 32 bit x86 threaded program.
Does anyone know why there doesn't appear to be any similar info
dumped for the thread info in 64 bit x86_64 threaded programs?
The pthread library uses the arch_prctl() service to setup the
segment registers there, and it would be handy for debuggers
to be able to recover the thread info in 64 bit core files as well.
next reply other threads:[~2010-10-20 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 14:31 Tom Horsley [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-20 11:52 [PATCH -mm 00/43] user_regset framework -- arch maintainers take note! Roland McGrath
2007-12-20 12:00 ` [PATCH -mm 42/43] x86 core dump TLS Roland McGrath
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=20101020103144.673c6bdc@tomh \
--to=tom.horsley@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