Hello Olly,
(gdb) bt #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #1 0x00007fa84248315f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78 #2 0x00007fa842435472 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x00007fa84241f4b2 in __GI_abort () at ./stdlib/abort.c:79 #4 0x00007fa84276d5dd in () #5 0x0000000000000000 in () I read that as it's already aborting when it segfaults, so maybe that's not helpful in knowing the root cause. I'm happy to debug further if someone tells me what to try.
This means the instruction just before 0x7fa84276d5dd is most probably a call to function abort. Usually this is done if some assertion fails. Therefore there might something like "assertion failed" in the logs at this time. Unfortunately 0x7fa84276d5dd might be inside of a shared object. And for it is no -dbgsym package installed. To find out which shared object you might have a look into the output of `info share`. If you receive such a crash you could create a core dump with gdb command `generate-core-file`. Or install some core dump collector, e.g. systemd-coredump. With this after a crash happened one can inspect it via coredumpctl list coredumpctl gdb This link contains some more ways to debug and to install the dbgsym packages: https://wiki.debian.org/HowToGetABacktrace Kind regards, Bernhard
