Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
WSJTX Segmentation fault
Seems to be WSJTX related. There's mentions of it over on the WSJTX groups.io.
gdb produces this: Thread 1 "wsjtx" received signal SIGSEGV, Segmentation fault. 0xb58f8c40 in QtPrivate::qustrchr(QStringView, unsigned short) () ?? from /lib/arm-linux-gnueabihf/libQt5Core.so.5 I'll wait for an update, hopefully there's a fix. 73 Andrew, K1YMI |
Yep, built from source. Well it seems to be running fine ATM. Not sure why it was acting up before. Whatever it was, I'm not going to touch it and move on and consider it a win for now... till the issue re-appears ;) On Tue, 2021-12-28 at 17:32 -0800, S Johnson wrote:
|
I don't know how to see a segmentation fault but since building a new BAP image that loaded WSJTX v2.5.3 (after modifying the BAP script), my WSJTX won't run? for more than a minute before shutting down (or being shut down)..? So, I might be experiencing the same problem as your are reporting.
Bullseye, WSJX v2.5.3, Icom 7000 running FLRIg and Signalink USB |
You can run wsjtx from command line and you'll see the error there when it crashes... Or run it using gdb debugger. Mine is also back to crashing...? Andrew, K1YMI On Tue, Dec 28, 2021, 20:53 Andrew via <anpepper=[email protected]> wrote:
|
to navigate to use esc to dismiss