From 2b363e104f9ceeb6cc1a4cf787ea7c9f0f60fcc6 Mon Sep 17 00:00:00 2001 From: moneromooo-monero Date: Fri, 8 Sep 2017 18:41:27 +0100 Subject: [PATCH] README.md: add instructions to fix core pattern --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 3f9b772d1..87d4ec2cb 100644 --- a/README.md +++ b/README.md @@ -426,9 +426,11 @@ Type `thread apply all bt` within gdb in order to obtain the stack trace Enter `ulimit -c unlimited` on the command line to enable unlimited filesizes for core dumps +Enter `echo core | sudo tee /proc/sys/kernel/core_pattern` to stop cores from being hijacked by other tools + Run the build. -When it terminates with an output along the lines of "Segmentation fault (core dumped)", there should be a core dump file in the same directory as monerod. +When it terminates with an output along the lines of "Segmentation fault (core dumped)", there should be a core dump file in the same directory as monerod. It may be named just `core`, or `core.xxxx` with numbers appended. You can now analyse this core dump with `gdb` as follows: