bitcoin: b-msghand[4988] general protection fault
Is there an existing issue for this?
- I have searched the existing issues
Current behaviour
Hello dear devs, I caught segfault today, running latest Bitcoin Code in full node mode on AMD64 Linux server.
Expected behaviour
no segfault
Steps to reproduce
I had not seen bitcoind crash for a long time. It’s a rare one I guess.
Relevant log output
dmesg:
traps: b-msghand[4988] general protection fault ip:55783548b790 sp:7f57627f3978 error:0 in bitcoind[557834c96000+aee000]
gdb backtrace: debug.txt
How did you obtain Bitcoin Core
Pre-built binaries
What version of Bitcoin Core are you using?
v27.0.0
Operating system and version
Debian GNU/Linux 12 (bookworm)
Machine specifications
Debian Stable server with AMD Ryzen 7 1700 and ECC RAM, everything stable and reliable. Bitcoin Core is using Tor and I2P network only, running in full mode. Blocks on RAID10 array, hardware is reliable.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 16 (10 by maintainers)
The main issue here is no core dump (in future please try and include it in the issue), and I don’t think there’s anything we can do with the gdb backtrace. I tested that using the 27.0 binary, and the associated debug symbols, works for inspecting a core dump. i.e:
Give GDB
bitcoindand the dump:No symbols. Return
bitcoind.dbg.txttobitcoind.dgband retry. Note that GDB will load the debug symbols automatically, but they can also be passed explicitly:https://codeberg.org/pkal/trip
Of course, sorry for not including it earlier. I am attaching first and last 100 lines of the log. In between, there is nothing useful, I think. At the end of the log, you will see nothing logged around time of the crash, unfortunately.
bitcoind.log
Was there anything unusual in the debug log before the crash?