On 27/11/2019 16:41, Karl Heinz Kremer wrote:
Bill,
yes, it happens every time. Here is what I do:
1) Bring up wsjtx with rig configured as FT-857 while flrig is running
- this means the app cannot connect to the serial port and will prompt
me to edit the configuration
2) Change rig type to flrig (using localhost:12345)
3) Click on "Test CAT"
4) That usually causes the problem - if not, change the frequency and
that will cause the problem
I just did this again, and ended up with the following trace
(slightly different than before):
[New Thread 0x97072340 (LWP 6044)]
[Detaching after fork from child process 6045]
[Thread 0x98074340 (LWP 6042) exited]
[Thread 0x97873340 (LWP 6043) exited]
free(): double free detected in tcache 2
Thread 12 "QThread" received signal SIGABRT, Aborted.
[Switching to Thread 0x95d1e340 (LWP 6038)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0xb569cf24 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:50
#1 0xb5688230 in __GI_abort () at abort.c:79
#2 0xb56d851c in __libc_message (action=action@entry=do_abort,
fmt=<optimized out>) at ../sysdeps/posix/libc_fatal.c:181
#3 0xb56df044 in malloc_printerr (str=<optimized out>) at malloc.c:5341
#4 0xb56e1098 in _int_free (av=av@entry=0xb57bb7d4 <main_arena>,
p=p@entry=0x95407cb8, have_lock=have_lock@entry=1) at malloc.c:4193
#5 0xb56e3a04 in _int_realloc
(av=av@entry=0xb57bb7d4 <main_arena>, oldp=oldp@entry=0x95407cb8,
oldsize=oldsize@entry=16, nb=nb@entry=24) at malloc.c:4615
#6 0xb56e4de8 in __GI___libc_realloc (oldmem=0x95407cc0, bytes=15) at
malloc.c:3222
#7 0x002466c0 in modeMapAdd ()
#8 0x00247478 in flrig_open ()
#9 0x00228484 in rig_open ()
HI Karl Heinz,
that crash is a different free() call, that tends to confirm heap
corruption.
The next step is probably to try and reproduce using the Hamlib rigctl
command line tool. Creating a debug build of Hamlib is fairly
straightforward. Debugging with an instance of WSJT-X is somewhat more
complex. There is a build of rigctl (called rigctl-wsjtx) packaged with
WSJT-X, try using that for starters, it looks this crash is while
opening the rig connection, the prior one was later in the process
setting the rig's VFO frequency.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
