> 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
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)
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=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
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.
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
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
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
> 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:
2021
> 21:21 To: wsjt-devel@lists.sourceforge.net
> Cc: Black Michael
> Subject: Re: [wsjt-devel] Reproducing 2.5.3 /4 crash WSJT-x
>
>
>
>
> There's a problem duplicating this error...I tried a loopback test
> here and no crashes
>
>
> So
Hard to test all the corner cases like suffixes under what appear to be certain
circumstances.
One of the problems I have with hamlib is I get no testing until WSJT-X or JTDX
get released.
I have 264 rigs now to support and can't test but a few.
The git log isn't very helpful and since it's not
On 21/12/2021 8:04 am, Black Michael via wsjt-devel wrote:
Well yes it's multi-threaded. Don't believe that's the underlying
cause though.
Is there a common rig maybe?
So far we have 1 IC-7300.
Or a common OS?
Or a common 32/64-bit version?
For those that have seen this problem please
> On 12/20/2021 2:15 PM Dana Myers via wsjt-devel
> wrote:
>
> Rig: IC-7300
> OS: Windows 11 Pro 21H2 64-bit
> 32/64 WSJT-X: WSJT-X 2.5.3 64-bit
> Other software running: notably, JT Alert 2.50.9
>
> When the crash happens, it's at the end of a receive period where
On 12/20/2021 1:04 PM, Black Michael via wsjt-devel wrote:
Well yes it's multi-threaded. Don't believe that's the underlying cause though.
Is there a common rig maybe?
So far we have 1 IC-7300.
Or a common OS?
Or a common 32/64-bit version?
For those that have seen this problem please
a
possible setting issue.
73, Reino OH3mA
*From:*Black Michael via wsjt-devel
[mailto:wsjt-devel@lists.sourceforge.net]
*Sent:* 20. joulukuutata 2021 21:21
*To:* wsjt-devel@lists.sourceforge.net
*Cc:* Black Michael
*Subject:* Re: [wsjt-devel] Reproducing 2.5.3 /4 crash WSJT-x
There's a problem
Mike,
It appears that it is necessary to have decoded something (anything??
) in a receive cycle for that test crash to occur.
AL, K0VM
On 12/20/2021 1:21 PM, Black Michael via wsjt-devel wrote:
There's a problem duplicating this error...I tried a loopback test
here and no crashes
Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: 20. joulukuutata 2021 21:21
To: wsjt-devel@lists.sourceforge.net
Cc: Black Michael
Subject: Re: [wsjt-devel] Reproducing 2.5.3 /4 crash WSJT-x
There's a problem duplicating this error...I tried a loopback test here
H3mA
>
>
>
>
>
>From: Black Michael via wsjt-devel
> [mailto:wsjt-devel@lists.sourceforge.net]
>Sent: 20. joulukuutata 2021 21:21
>To: wsjt-devel@lists.sourceforge.net
> Cc: Black Michael
>
-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: 20. joulukuutata 2021 21:21
To: wsjt-devel@lists.sourceforge.net
Cc: Black Michael
Subject: Re: [wsjt-devel] Reproducing 2.5.3 /4 crash WSJT-x
There's a problem duplicating this error...I tried a loopback test here and no
crashes
So
There's a problem duplicating this error...I tried a loopback test here and no
crashes
Soquestion for those seeing this problem.
For Dana...it sounds like you did a restart of WSJT-X and duplicated the
problem, right?
So maybe there's a setting in WSJT_X that is related.
Can you send your
Hello,
I'm seeing a crash - twice a moment ago - when W9YOY/M called me. Using 2.5.3.
Also running
JT-Alert for WSJT-X
Perhaps related?
73,
Dana K6JQ
On 12/17/2021 7:43 AM, Al via wsjt-devel wrote:
( wsjt-x 2.5.3, W11 )
Set mode FT8
Enter DX call K0VQM/4
Generate Std Msgs
select Next 'TX
More...
Joe,
Really weird...
It appears that it is also necessary to actually decode something (
anything ?? ) during the RX cycle in order for it to crash during the TX
cycle.
Attached is my .ini file which crashes during TX3 if I also have
decodes during RX..
AL, K0VM
On
Joe,
I attempted to reproduce from a default configuration with minimal
amendments. It crashed one time only.
Then reverted to my normal configuration and I can no longer replicate.
I'll Let you know if I find something else.
AL, K0VM
On 12/17/2021 10:42 AM, Joe Taylor via wsjt-devel
Hi Stephen,
The window-size behavior has been discussed on this list before. I have
nothing new to add.
On your "+.055" frequency-setting issue, please send me a copy of the
file WSJT-X.ini in your log directory.
-- Joe, K1JT
On 12/17/2021 11:44 AM, Stephen Mitchell via wsjt-devel
Hi Stephen,
The window-size behavior has been discussed on this list before. I have
nothing new to add.
On your "+.055" frequency-setting issue, please send me a copy of the
file WSJT-X.ini in your log directory.
-- Joe, K1JT
On 12/17/2021 11:44 AM, Stephen Mitchell via
Hi Al,
Thanks for the report. Unfortunately, as shown in the attached screen
shot, I can't seem to reproduce the bug here, by using your recipe.
We have not yet found a reliable way to trigger this fault, or to
diagnose it.
-- Joe, K1JT
On 12/17/2021 10:43 AM, Al via wsjt-devel
( wsjt-x 2.5.3, W11 )
Set mode FT8
Enter DX call K0VQM/4
Generate Std Msgs
select Next 'TX 3'
enable TX
WSJT will crash on second or third transmission attempt
AL, K0VM___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
27 matches
Mail list logo
