On 30/05/2016 15:03, Jim Bennett wrote:
> Just gave it another try. Rebooted the RPI just to be sure I was on a
> clean slate. Opened a terminal window, entered WSJTX and it ran
> exactly as yesterday: several of the spurious ALSA messages and then
> nothing. No other Windows hiding anywhere. Had to CTRL-C out of it.
>
> To be sure the KX3 or the external sound card were not the culprits, I
> started up FLDIGI and it ran successfully.
>
> So, what are my next steps to see what WSJT-X is doing?
Hi Jim,
you really need a debug configuration build of WSJT-X to see what is
happening but let's try first with the build you have. Load the wsjtx
executable under the control of gdb from a terminal session:
gdb <path-to-wsjtx-bin-directory>/wsjtx
then run the program:
(gdb) r
when you are sure WSJT-X has hung or whatever it is doing, press CTRL+C
(type the CTRL+C into the terminal session that is running gdb). It
should drop back to gdb. Get a thread report and backtrace:
(gdb) info threads
thread info is printed ....
(gdb) bt
backtrace of current thread is printed ...
and report back here with what it prints.
73
Bill
G4WJS.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
