Please Help for debug coredump after latest zypper dup
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
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.
Il 22/03/22 00:52, Luciano Santos ha scritto:
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. Yes exactly Luciano (I guess you are Brazilian or may be Portuguese) WSJT-X is an amateur radio application developed by Joe Taylor, an American astrophysicist and Nobel Prize and amateur radio too 😉.
I tried also running strace but my knowledge of the debugging tools is pretty limited. I recompiled wsjtx against the latter TW updates without success. At the end the issue has been resolved simply uninstalling a plethora of Qt packages and then reinstalling it in small groups just for restoring the normal usage of my system, I.E. the Yast Qt... So I really haven't discover the precise cause of the SIGSEGV of wsjtx but it was certainly been caused by some of the "Qt" packages that after I uninstalled. Regards, -- Marco Calistri Build: openSUSE Tumbleweed 20220320 Kernel:5.16.14-1-default Desktop: XFCE (4.16.0)
Marco Calistri wrote:
Yes exactly Luciano (I guess you are Brazilian or may be Portuguese) WSJT-X is an amateur radio application developed by Joe Taylor, an American astrophysicist and Nobel Prize and amateur radio too 😉.
And I'm guessing you're Italian.
At the end the issue has been resolved simply uninstalling a plethora of Qt packages and then reinstalling it in small groups just for restoring the normal usage of my system, I.E. the Yast Qt...
That's interesting, from the brief look I had at the WSJT-X's compilation help I saw some QT requirements. But now it's hard to tell what's what since we don't know whether the recompilation may have helped or not here.
So I really haven't discover the precise cause of the SIGSEGV of wsjtx but it was certainly been caused by some of the "Qt" packages that after I uninstalled.
Well, next time will be armed with knowledge. Personally I like to use systemd-coredump, since it automates/make things easier to analyze coredumps, it downloads the required debuginfo packages so GDB's backtrace are meaningful, aside from information about the shared libraries involved when the core that got dumped. You can take a look at those resources to get some basics about SIGSEGV + GDB: http://www.unknownroad.com/rtfm/gdbtut/gdbsegfault.html and https://www.baeldung.com/linux/segmentation-fault Those may give you a bit of an idea of what possibly went wrong with WSJT-X.
Il 23/03/22 19:36, Luciano Santos ha scritto:
Marco Calistri wrote:
Yes exactly Luciano (I guess you are Brazilian or may be Portuguese) WSJT-X is an amateur radio application developed by Joe Taylor, an American astrophysicist and Nobel Prize and amateur radio too 😉. And I'm guessing you're Italian. Bingo 😁 At the end the issue has been resolved simply uninstalling a plethora of Qt packages and then reinstalling it in small groups just for restoring the normal usage of my system, I.E. the Yast Qt... That's interesting, from the brief look I had at the WSJT-X's compilation help I saw some QT requirements. But now it's hard to tell what's what since we don't know whether the recompilation may have helped or not here.
So I really haven't discover the precise cause of the SIGSEGV of wsjtx but it was certainly been caused by some of the "Qt" packages that after I uninstalled. Well, next time will be armed with knowledge.
Personally I like to use systemd-coredump, since it automates/make things easier to analyze coredumps, it downloads the required debuginfo packages so GDB's backtrace are meaningful, aside from information about the shared libraries involved when the core that got dumped.
You can take a look at those resources to get some basics about SIGSEGV + GDB:
http://www.unknownroad.com/rtfm/gdbtut/gdbsegfault.html andhttps://www.baeldung.com/linux/segmentation-fault
Those may give you a bit of an idea of what possibly went wrong with WSJT-X.
Thanks for the helpful information Luciano! Stay well, Um abraço! -- Marco Calistri Build: openSUSE Tumbleweed 20220321 Kernel:5.16.14-1-default Desktop: XFCE (4.16.0)
participants (2)
-
Luciano Santos
-
Marco Calistri