Cuberite segmentation fault
techtechnikov opened this issue · comments
Client version:1.12.2
Server OS: Linux
Cuberite Commit id: (Found at the top of the server's console output)
./Cuberite[0x4c787d]
/lib/x86_64-linux-gnu/libc.so.6(+0x3cef0)[0x7f16820a3ef0]
./Cuberite[0x42b342]
./Cuberite[0x6ce30b]
./Cuberite[0x6c14e1]
./Cuberite[0x6b9642]
./Cuberite[0x4be215]
./Cuberite[0x426b15]
./Cuberite[0x42fa95]
./Cuberite[0x4b818a]
./Cuberite[0x4b04e6]
./Cuberite[0x4b02af]
./Cuberite[0x6e066c]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xd3864)[0x7f1682319864]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8eae)[0x7f168245aeae]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f1682164a5f]
[20:11:12] Failure report:
:( | Cuberite has encountered an error and needs to close
| SIGSEGV: Segmentation fault
|
| Cuberite Jenkins x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Release (master) (id: #287)
| from commit 39392bbeaeb3d9bb3b338719e33a52844e792929
zsh: segmentation fault ./Cuberite
Ten minutes ago, I got an SegFault again. I think the bots crashes the server.
Could you try this steps with a debug build for a better stack trace?
https://forum.cuberite.org/thread-631.html