diff options
| author | moneromooo-monero <moneromooo-monero@users.noreply.github.com> | 2017-09-08 18:41:27 +0100 |
|---|---|---|
| committer | moneromooo-monero <moneromooo-monero@users.noreply.github.com> | 2017-09-08 18:41:27 +0100 |
| commit | 2b363e104f9ceeb6cc1a4cf787ea7c9f0f60fcc6 (patch) | |
| tree | 6885ad1fe69faadf34f94e1fb1282a0c118b682f | |
| parent | Merge pull request #2384 (diff) | |
| download | monero-2b363e104f9ceeb6cc1a4cf787ea7c9f0f60fcc6.tar.xz | |
README.md: add instructions to fix core pattern
| -rw-r--r-- | README.md | 4 |
1 files changed, 3 insertions, 1 deletions
@@ -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: |