> On 12/21/2021 12:27 PM Tom Berry via wsjt-devel
> wrote:
>
>
> On 12/21/2021 3:04 PM, Joe Taylor via wsjt-devel wrote:
> > Hi all,
> >
> > If you have seen a bug that can cause WSJT-X 2.5.3 to crash when
> > callsigns like W9YOY/M or K0VQM/4 are involved, please help us to
> > isolate and
I was able to reproduce this under WinDbg and using audio loopback and my own
callsign.It happened after the transmit of W9MDB R-20Which also
matches the behavior seen by Tom AA4VV Critical error detected c374
(6fbc.6fb8): Break instruction exception - code 8003 (first chance)
ntdll!RtlR
If you could please run WinDbg and attach it to the WSJT-X process.Maybe it
will tell us something.
https://www.microsoft.com/en-us/p/windbg/9pgjgd53tn86?rtc=1&activetab=pivot:overviewtab
Mike W9MDB
On Tuesday, December 21, 2021, 02:44:35 PM CST, Tom Berry via wsjt-devel
wrote:
On
On 12/21/2021 3:04 PM, Joe Taylor via wsjt-devel wrote:
Hi all,
If you have seen a bug that can cause WSJT-X 2.5.3 to crash when
callsigns like W9YOY/M or K0VQM/4 are involved, please help us to
isolate and fix it. What we really need is a sequence of steps that
will reliably reproduce the c
Hi Ton,
The crash you observed is caused by setting Rx frequency to a value so
high that the highest tone of the mode in use would be above 5000 Hz.
In general, WSJT-X is designed to work with maximum Rx passbands up to
5000 Hz, but not beyond. Best to stay within that limit.
-- 73,
Hi all,
If you have seen a bug that can cause WSJT-X 2.5.3 to crash when
callsigns like W9YOY/M or K0VQM/4 are involved, please help us to
isolate and fix it. What we really need is a sequence of steps that
will reliably reproduce the crash.
If you have seen this bug, please let us know. I
Hi Mike,
What is the rig that is being used when the crash occurs ?
73,
Sam W2JDB
-Original Message-
From: Black Michael via wsjt-devel
To: Joe Taylor via wsjt-devel
Cc: Black Michael
Sent: Tue, Dec 21, 2021 2:16 pm
Subject: Re: [wsjt-devel] Reproducing 2.5.3 /4 crash WSJT-x
Nope...t
Nope...tested several calls on loopback both on receiver and transmitter side
in both QSO directionsno problems.
The only common thread is the suffix it seems.
I even used one user's WSJT-X.ini file though I don't have his rig so had to
change that one thing.Ran the same test that he said cr
Hi Mike,
Have you had any success duplicating the problem some have seen with
calls like W9YOY/M or K0VQM/4 ? I have been unable to make v2.5.3
crash, using any of these recipes.
-- Joe
On 12/20/2021 2:21 PM, Black Michael via wsjt-devel wrote:
There's a problem duplicating this err
> On 12/20/2021 9:05 PM jarmo via wsjt-devel
> wrote:
>
>
> Mon, 20 Dec 2021 21:04:00 + (UTC)
> Black Michael via wsjt-devel
> kirjoitti:
>
> I compiled 2.5.3 and confirm, crashes randomly, with NO other
> explanations, that nigghtly log. Segmentation fault on these
> executables: WSJT
Sent Email last Friday, no response, trying again. Disregard if still in work.
Running the latest versions of WSJT-X and HRD with a Kenwood TS-850s and
signalink USB. When Transmitting WSJT Flips from the selected band on VFO-A to
the band selected on VFO-B. However HRD and my radio show transmi
11 matches
Mail list logo
