qT87DSMX9oW3Nuibod23

> The guix debug symbols are split from the `bitcoind` you are using. So someone would have download them before demangling. I tried to do that, but for some reason...

> > > Was there anything unusual in the debug log before the crash? > > > Logs contains nothing else worth mentioning, machine continues to run as intended. >...

> The debug symbols are separately produced by guix and the downloads are on https://bitcoincore.org/bin/bitcoin-core-27.1/. In this case it would be `x86_64-linux-gnu-debug`. That's great, thank you! Now I have upgraded...

Thanks for all the replies! @fanquake where I can get trip program? Couldn't find it anywhere in Debian Stable using apt-file search.

Thanks for fantastic instructions! I was able to trip bitcoind, and do full backtrace with proper symbols. Thanks! I will now await another crash, using upgraded bitcoin core 27.1. It...

I am also inclined to say this is hardware error. I had these and it turned out to be unreliable RAM. Put that database on Btrfs, it should never have...

> @Tajuras Which version of 25 are you running? I tried both 26.2 and 25.2 and I get the same problem with both. Have you memtested your machine yet?

> > Have you memtested your machine yet? > > I've been having trouble with getting the grub configuration correct to actually boot into it. I'll need to use a...

> > In my main machine, is ryzen with 32gb ddr4 with 2 sticks of memory. The other machine is Xeon, with 32gb memory, in quad channel ddr3. So i...

> hmm I have a small dbcache size I just noticed... can't remember why I set it to that. maybe the increased fsyncs is increasing the chance of a bug...