Still trying to figure out why everything works except FT8 transmit.
Any tools I could try to narrow this down?
Here's some data from valgrind when I try to transmit in FT8 mode:
==7994== Thread 1:
==7994== Conditional jump or move depends on uninitialised value(s)
==7994== at 0x124B18: __packjt_MOD_packmsg (in /usr/local/bin/wsjtx)
==7994==
==7994== Conditional jump or move depends on uninitialised value(s)
==7994== at 0x122AE0: __packjt_MOD_unpackmsg (in /usr/local/bin/wsjtx)
==7994==
....
And when I close the program:
==7994==
==7994== Thread 1:
==7994== Invalid free() / delete / delete[] / realloc()
==7994== at 0x484AB3C: free (vg_replace_malloc.c:530)
==7994== by 0x76A73: QVector<QColor>::~QVector() (in
/usr/local/bin/wsjtx)
==7994== Address 0x1010000 is 10877256 bytes inside data symbol "dec_data"
Without valgrind, I just get this as output when closing the program:
*** Error in `/usr/local/bin/wsjtx': free(): invalid pointer: 0x01010000 ***
On 11/28/2017 2:25 PM, Rob Clark wrote:
it does do it on a dummy load as well and also when the transmit power
is not enough to trigger VOX. Although I do need to correct my
previous post: it does not stop transmitting immediately. It
finishes the 15 seconds while the waterfall scrolls black. Hitting the
Halt TX button does _not_ halt that initial 15 second transmission.
Subsequent to that, it will not transmit FT8 or Tune, it will continue
to decode, and the waterfall scrolls black until a restart of WSJT-X.
JT9 and JT65 are absolutely fine, which is what puzzles me. - Rob, KK5NI
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
