diff options
| author | Riccardo Spagni <ric@spagni.net> | 2017-09-18 13:18:52 +0200 |
|---|---|---|
| committer | Riccardo Spagni <ric@spagni.net> | 2017-09-18 13:18:52 +0200 |
| commit | 4c202b199e0f107f600a65e9c21bde5c270b9f4f (patch) | |
| tree | d71799266ffe22b0c6de8a745246fd30f972cb66 | |
| parent | Merge pull request #2174 (diff) | |
| parent | README.md: add instructions to fix core pattern (diff) | |
| download | monero-4c202b199e0f107f600a65e9c21bde5c270b9f4f.tar.xz | |
Merge pull request #2416
2b363e10 README.md: add instructions to fix core pattern (moneromooo-monero)
| -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: |