Re: [wsjt-devel] Bugs in command line tools in WSJTX 1.8.0-rc1

2017-07-11 Thread Steven Franke
Dani - 
We are aware of the fact that the command line tools are not stable at the 
moment. They will be cleaned up and tested before the GA release.
Steve, k9an

> On Jul 11, 2017, at 3:52 PM, Dani EA4GPZ  wrote:
> 
> Hi all,
> 
> I have compiled WSJTX 1.8.0-rc1 from source an I'm finding the following
> bugs in the command line tools.
> 
> jt9 will always segfault when run for JT9:
> 
> 
> $ jt9 -9 00_01.wav
> 
> Program received signal SIGSEGV: Segmentation fault - invalid memory
> reference.
> 
> Backtrace for this error:
> #0  0x7F9211B1DD98
> #1  0x7F9211B1CF30
> #2  0x7F92108100CF
> #3  0x4110F0 in symspec_
> #4  0x406D52 in MAIN__ at jt9.f90:?
> Segmentation fault
> -
> 
> ft8d will also segfault always:
> 
> ---
> $ ft8d 40 2 00_01.wav
> 
> Program received signal SIGSEGV: Segmentation fault - invalid memory
> reference.
> 
> Backtrace for this error:
> #0  0x7F4C03C8ED98
> #1  0x7F4C03C8DF30
> #2  0x7F4C029810CF
> #3  0x414C60 in bpdecode174_
> #4  0x403A5D in ft8b_
> #5  0x402693 in MAIN__ at ft8d.f90:?
> Segmentation fault
> -
> 
> ft8sim doesn't seem to work properly. When run as suggested in the example:
> 
> ft8sim "K1ABC W9XYZ EN37" 0.0 0.1 1.0   10   -18
> 
> all the samples of the generated wav file are 0.
> 
> 
> When run as
> 
> ft8sim "EA4GPZ M0HXM IO94" 0.0 0.0 0.0 1 0
> 
> there is noise and a signal in the generated wav file, but the signal is
> not valid FT8 (it covers more than 2kHz of spectrum).
> 
> 
> 73,
> 
> Dani.
> 
> --
> 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


--
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


[wsjt-devel] Bugs in command line tools in WSJTX 1.8.0-rc1

2017-07-11 Thread Dani EA4GPZ
Hi all,

I have compiled WSJTX 1.8.0-rc1 from source an I'm finding the following
bugs in the command line tools.

jt9 will always segfault when run for JT9:


$ jt9 -9 00_01.wav

Program received signal SIGSEGV: Segmentation fault - invalid memory
reference.

Backtrace for this error:
#0  0x7F9211B1DD98
#1  0x7F9211B1CF30
#2  0x7F92108100CF
#3  0x4110F0 in symspec_
#4  0x406D52 in MAIN__ at jt9.f90:?
Segmentation fault
-

ft8d will also segfault always:

---
$ ft8d 40 2 00_01.wav

Program received signal SIGSEGV: Segmentation fault - invalid memory
reference.

Backtrace for this error:
#0  0x7F4C03C8ED98
#1  0x7F4C03C8DF30
#2  0x7F4C029810CF
#3  0x414C60 in bpdecode174_
#4  0x403A5D in ft8b_
#5  0x402693 in MAIN__ at ft8d.f90:?
Segmentation fault
-

ft8sim doesn't seem to work properly. When run as suggested in the example:

ft8sim "K1ABC W9XYZ EN37" 0.0 0.1 1.0   10   -18

all the samples of the generated wav file are 0.


When run as

ft8sim "EA4GPZ M0HXM IO94" 0.0 0.0 0.0 1 0

there is noise and a signal in the generated wav file, but the signal is
not valid FT8 (it covers more than 2kHz of spectrum).


73,

Dani.

--
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