On 28/05/2020 10:16, Michael Kerrisk (man-pages) wrote:
Hello Jonny,
On 5/27/20 5:22 PM, Jonny Grant wrote:
On 27/05/2020 14:32, Michael Kerrisk (man-pages) wrote:
Hi Jonny
On Wed, 27 May 2020 at 15:23, Jonny Grant <jg@xxxxxxxx> wrote:
On 27/05/2020 14:06, Michael Kerrisk (man-pages) wrote:
Hi Jonny,
On Mon, 25 May 2020 at 17:08, Jonny Grant <jg@xxxxxxxx> wrote:
Suggestion for some additional information on this page:
http://man7.org/linux/man-pages/man5/core.5.html
Could "Core dumps and systemd" be extended to give an
example of sysctl making a temporary change?
eg set to the filename and signal that causes the core dump:
# sysctl -w kernel.core_pattern="%e-%s.core"
I'm a little confused: what do you mean by "making a *temporary*
change" (i.e., where does "temporary" come into it)?
Thanks,
Michael
As I understood, this core pattern is set until reboot.
Okay, now I understand. Next question: what's the value in having the
signal number in the filename?
The signal number indicates the reason the core was dumped, > eg 11 SIGSEGV, SIGTRAP is 5.
Sure, it tells us what signal triggered the core dump.
My reason for the question was that it doesn't tell us the
*reason* for the core dump--for example, SIGSEGV can be
generated for many reasons.
Yes you're right. I'm sure you know all this already, there are a few crash handlers that uses gdb to generate a
backtrace automatically.
Thank you for adding the change
Jonny
