Marco Calistri wrote:
Hello, What can be the cause for coredump of the wsjtx program after latest TW zypper dup? Follows the gdb output: Starting program: /home/marco/WSJT-X_build/.wsjtx/bin/wsjtx [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7ffff1fb4640 (LWP 4431)] [New Thread 0x7ffff1504640 (LWP 4432)] [New Thread 0x7ffff0cfc640 (LWP 4439)] Thread 1 "wsjtx" received signal SIGSEGV, Segmentation fault. 0x00007ffff5b96849 in malloc_consolidate (av=av@entry=0x7ffff5cfeaa0
) at malloc.c:4715 4715 { Many thanks!
Hello Marco! What'd be more useful for people to see would be a stack trace. Fedora has a nice article on that: https://fedoraproject.org/wiki/StackTraces#gdb However, it seems you have compiled this software on your machine, from the looks of it, is that right? If so, the most probable cause of this SIGSEGV is that some of the wsjtx's dependency got updated and it needs to be recompiled to point to the newer library(ies) that got updated.