From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Jonny Grant <jg@jguk.org>, linux-man <linux-man@vger.kernel.org>
Cc: mtk.manpages@gmail.com
Subject: Re: core man page %e
Date: Tue, 9 Jun 2020 12:18:10 +0200 [thread overview]
Message-ID: <2c72b844-c99f-ec66-02a9-a12d688ece13@gmail.com> (raw)
In-Reply-To: <ae5293ba-17dd-fd6d-54b0-312a008e3167@jguk.org>
Hello Jonny,
On 5/30/20 12:39 PM, Jonny Grant wrote:
> 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
I changed it to this:
%e The process or thread's comm value, which typically is the
same as the executable filename (without path prefix, and
truncated to a maximum of 15 characters), but may have
been modified to be something different; see the discus‐
sion of /proc/[pid]/comm and /proc/[pid]/task/[tid]/comm
in proc(5).
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-06-09 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 10:39 core man page %e Jonny Grant
2020-06-01 10:21 ` 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) [this message]
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=2c72b844-c99f-ec66-02a9-a12d688ece13@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=jg@jguk.org \
--cc=linux-man@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;
as well as URLs for NNTP newsgroup(s).