On 01/05/2019 21:09, Christoph Berg wrote:
If that doesn't help then I can send you an instrumented version of WSJT-X
to track the CAT communication in detail, or explain how to enable that in
your own build.
I guess it's WSJT_TRACE_CAT && WSJT_TRACE_CAT_POLLS? I can try that
tomorrow.
Hi Christoph,
setting those options ON will work for a debug configuration build. To
get the trace working in a release configuration build you need
WSJT_QDEBUG_IN_RELEASE=ON, and you can have the debug trace redirected
to a file by setting WSJT_QDEBUG_TO_FILE=ON (the trace will be appended
to /tmp/WSJT-X_trace.log). Another option that can help is
WSJT_HAMLIB_VERBOSE_TRACE=ON , set that and you will get the equivalent
of -vvvvv for the Hamlib trace.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
