From: Jonny Grant <jg@jguk.org>
To: Michael Kerrisk <mtk.manpages@gmail.com>,
linux-man <linux-man@vger.kernel.org>
Subject: core man page %e
Date: Sat, 30 May 2020 11:39:57 +0100 [thread overview]
Message-ID: <ae5293ba-17dd-fd6d-54b0-312a008e3167@jguk.org> (raw)
Hello mtk
I've noticed "%e-%s.core" often gives something other than the filename and the name is truncated to 16 bytes:-
ThreadPoolServi-5.core
Chrome_InProcUt-5.core
This was set:
sysctl -w kernel.core_pattern="%e-%s.core"
In multithreaded applications it looks like %e is giving something other than the filename, perhaps a thread entry-point
symbol name.
https://www.man7.org/linux/man-pages/man5/core.5.html
%e executable filename (without path prefix)
Could this be updated to:
%e executable filename or thread name truncated to 16 bytes
Cheers, Jonny
next reply other threads:[~2020-05-30 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 10:39 Jonny Grant [this message]
2020-06-01 10:21 ` core man page %e Jonny Grant
2020-06-09 8:25 ` Michael Kerrisk (man-pages)
2020-06-09 11:00 ` Jonny Grant
2020-06-09 10:18 ` Michael Kerrisk (man-pages)
2020-06-09 11:35 ` Jonny Grant
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=ae5293ba-17dd-fd6d-54b0-312a008e3167@jguk.org \
--to=jg@jguk.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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;
as well as URLs for NNTP newsgroup(s).