Hi All,
I found several command that cause a "Program received signal SIGSEGV,
Segmentation fault.", but it can be caused by work in progress.
(JTSDK-QT 5.5 ) C:\JTSDK\zzloc\install\Debug\bin)ft8code -t
Message Decoded Err? Type
----------------------------------------------------------------------------
At line 1 of file C:\JTSDK\zzloc\src\lib\ft8\genft8.f90
Fortran runtime error: Actual string length is shorter than the declared
one for dummy argument 'msg37' (0/37)
(JTSDK-QT 5.5 ) C:\JTSDK\zzloc\install\Debug\bin)msk144code -t
Message Decoded Err? Type
--------------------------------------------------------------------------
**.
* 0:
At line 39 of file C:\JTSDK\zzloc\src\lib\msk144code.f90
Fortran runtime error: Index '65537' of dimension 1 of array 'testmsg'
above upper bound of 75
I try to switch to MKS144 mode, in a new enviroment (wsjtx -r ZZ)
Seem that I cannot switch to that mode without a crash.
The most strange error is gdb error.
Windows 10 1803 build SO 17134.285
QT 5.5 from JTSDK
Programs compiled from source in debug mode
(JTSDK-QT 5.5 ) C:\JTSDK\zzloc\install\Debug\bin)gdb --args
C:/JTSDK/zzloc/install/Debug/bin/wsjtx -r ZZ
GNU gdb (GDB) 7.8.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from C:/JTSDK/zzloc/install/Debug/bin/wsjtx...done.
(gdb) run
Starting program: C:\JTSDK\zzloc\install\Debug\bin\wsjtx.exe -r ZZ
[New Thread 4860.0x1eb8]
[New Thread 4860.0x20b8]
[New Thread 4860.0x214c]
[New Thread 4860.0x1c64]
[New Thread 4860.0x1e3c]
[New Thread 4860.0x27ac]
[New Thread 4860.0x16f4]
[New Thread 4860.0x1780]
[New Thread 4860.0x1a64]
[New Thread 4860.0x598]
[New Thread 4860.0x1954]
[New Thread 4860.0x2250]
[New Thread 4860.0x1738]
[New Thread 4860.0x3c0]
[New Thread 4860.0x1a44]
[New Thread 4860.0x1ed4]
[New Thread 4860.0x18b4]
[New Thread 4860.0x1e4c]
[New Thread 4860.0x938]
[Thread 4860.0x1a64 exited with code 0]
[Thread 4860.0x598 exited with code 0]
[New Thread 4860.0x5d0]
[New Thread 4860.0x1180]
[New Thread 4860.0x26a4]
[New Thread 4860.0x1d4]
[Thread 4860.0x214c exited with code 0]
[Thread 4860.0x1c64 exited with code 0]
[Thread 4860.0x20b8 exited with code 0]
[Thread 4860.0x1ed4 exited with code 0]
Program received signal SIGSEGV, Segmentation fault.
0x004fa009 in msk40decodeframe (c=..., mycall=..., hiscall=...,
xsnr=-4.50094604, bswl=.TRUE.,
nhasharray=<error reading variable: Cannot access memory at address
0x5d1f440>, recent_calls=
../../../../src/gdb-7.8.1/gdb/utils.c:1062: internal-error: virtual
memory exhausted.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n
This is a bug, please report it. For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.
../../../../src/gdb-7.8.1/gdb/utils.c:1062: internal-error: virtual
memory exhausted.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
Command aborted.
(gdb)
--
73
Sandro
IW3RAB
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
