wart-node crashed

[kr1z1s]

I've tried different versions wart-node - 0.9.6, 0.8.14, 0.8.10

[6599951.262879] wart-node[2821541]: segfault at 7fbb67491b80 ip 00000000005ce24f sp 00007ffc99b83ca0 error 6
[6599951.262892] Code: 66 0f ef c0 53 48 89 f3 48 83 ec 08 89 56 10 48 8d 57 10 48 89 7e 08 c7 46 58 08 00 00 00 48 89 56 20 48 8b 57 18 48 89 56 28 <48> 89 02 48 89 47 18 48 8b 05 fb 02 1f 00 0f 11 46 68 48 89 86 e8

OS - Ubuntu Server 22.04

[CoinFuMasterShifu]

Do you have any more additional informataion?

[kr1z1s]

Do you have any more additional informataion?

Ok
I run wart-node with valgrind. I'm waiting crash

[kr1z1s]

Do you have any more additional informataion?

==709365== Access not within mapped region at address 0xE0000022
==709365== at 0x9F4C63: ???
==709365== by 0x4784B6: ???
==709365== by 0x4FD9137: ???
==709365== by 0x4FD907F: ???
==709365== by 0x267: ???
==709365== If you believe this happened as a result of a stack
==709365== overflow in your program's main thread (unlikely but
==709365== possible), you can try to increase the size of the
==709365== main thread stack using the --main-stacksize= flag.
==709365== The main thread stack size used in this run was 8388608.
==709365==
==709365== HEAP SUMMARY:
==709365== in use at exit: 0 bytes in 0 blocks
==709365== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==709365==
==709365== All heap blocks were freed -- no leaks are possible
==709365==
==709365== ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
==709365==
==709365== 1 errors in context 1 of 4:
==709365== Invalid read of size 8
==709365== at 0x9F4C63: ???
==709365== by 0x4784B6: ???
==709365== by 0x4FD9137: ???
==709365== by 0x4FD907F: ???
==709365== by 0x267: ???
==709365== Address 0xe0000022 is not stack'd, malloc'd or (recently) free'd
==709365==
==709365==
==709365== 1 errors in context 2 of 4:
==709365== Invalid write of size 8
==709365== at 0x5B3FB5: ???
==709365== by 0x4FD96CF: ???
==709365== by 0xA7: ???
==709365== Address 0x4fd90f8 is on thread 5's stack
==709365== 1272 bytes below stack pointer
==709365==
==709365==
==709365== 1 errors in context 3 of 4:
==709365== Invalid write of size 1
==709365== at 0x5B3FAC: ???
==709365== by 0x4FD96CF: ???
==709365== by 0xA7: ???
==709365== Address 0x4fd90f0 is on thread 5's stack
==709365== 1280 bytes below stack pointer
==709365==
==709365==
==709365== 1 errors in context 4 of 4:
==709365== Invalid read of size 1
==709365== at 0x5B3EF4: ???
==709365== by 0x4FD96CF: ???
==709365== by 0xA7: ???
==709365== Address 0x4fd90f0 is on thread 5's stack
==709365== 1280 bytes below stack pointer
==709365==
==709365== ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
Segmentation fault (core dumped)

[CoinFuMasterShifu]

Sorry for the late reply, somehow I missed this message. You need to run with debug build to get more detailed information for me. Do you know how to do this?

[kr1z1s]

Sorry for the late reply, somehow I missed this message. You need to run with debug build to get more detailed information for me. Do you know how to do this?

Debug build? I don't know.

[CoinFuMasterShifu]

You need to compile from source. To do this, you need to have a recent compiler and download the Warthog repository with git and compile with meson. I can give you detailed steps if you need. The valgrind output shows "???" because there is no debug information about the source code in the precompiled binary that you can download from the website.

[kr1z1s]

You need to compile from source. To do this, you need to have a recent compiler and download the Warthog repository with git and compile with meson. I can give you detailed steps if you need. The valgrind output shows "???" because there is no debug information about the source code in the precompiled binary that you can download from the website.

I have compiled and run debug version.
But it has been working for a long time and does not crash.
I'm waiting. If there is no more crash, then I will use this version.

[CoinFuMasterShifu]

Thank you for your effort. Just leave it running for some time. It could be possible that it is a heisenbug, i.e. a bug which disappears when you try to observe it.