Dear wsjtx Devlop team.
I uploaded it as a topic to wsjtx group but it did not go up well. then
send you an e-mail to find this e-mail address on the Internet. It seems to
be the first time I've used the Yahoo group.
----------------------------------------
First I love wsjtx too much.I restarted the amateur radio because of the
jt65 and ft8.
I found a problem while customizing wsjtx in Raspberry Pi.
The other mode works normally, but only the toxic FT8 has a problem.
FT8 was not TX. Sometimes it was Send Message, but the program was forced
to stop.
The compiled distribution worked normally and I suspected myself.
I use the latest compiler with 1.8.0 source and latest commit source.
tested several things and they all had the same problem.
While analyzing the source, I noticed an overflow in FT8.
Because of the 12-byte overflow, it is possible that anomalies may occur in
other operating systems such as Windows, linux.
Issue position :
in mainwindow.cpp
char volatile ft8msgbits[75]; //packed 75 bit ft8 message
solve
in mainwindow.cpp
char volatile ft8msgbits[87]; //fixed by KD8CEC overflow
memory, 75 + CRC = 87 //packed 75 bit ft8 message
A pointer overflow causes a problem where strange values are placed in
adjacent variables.
There will be some differences depending on the compiler and the operating
system, but if there is overflow of 12 bytes, there will be other variables.
Fixed the above code and solved all issues that occurred in FT8 mode.
If this is a problem you already know, ignore this mail.
Thanks.
73
Ian Lee KD8CEC
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
