Hello,
I have verified that the bug has been resolved back on version
2.2.0, but for me it is still present despite the presence of the
"refspec.dat" file.
Release: WSJT-X 2.2.0-rc2
May 25, 2020
-
WSJT-X 2.2.0-rc2 is
That has been fixed in hamlib 4.3.1 and the 4.4 version too.
So it will be in the release of WSJTX.
Compile hamlib from herehttps://github.com/Hamlib/Hamlib/releases/tag/4.3.1
Mike W9MDB
On Sunday, September 19, 2021, 02:05:39 PM CDT, Alex Lelievre via
wsjt-devel wrote:
Hi there,
Hi there,
I launched WSJT-X 2.5.0 rc6 this morning and forgot to turn on my radio. This
caused the app to crash which I believe might be a new bug. My version of
WSJT-X was built locally from source (release build).
Here’s the relevant part of the crash log (which I still have in case
Hi Mike,
Was running 2.4.0-rc3 tonight testing with another station We made some
contacts I was on RC1 and he was on rc2 on submode B. We both upgraded
to rc3. We decided to see what would happen on Submode C. I was on
T/R=15sec and left it there so the Tx Freq box turned red, no surprise
Hi guys,
Was running 2.4.0-rc3 tonight testing with another station We made some
contacts I was on RC1 and he was on rc2 on submode B. We both upgraded to rc3.
We decided to see what would happen on Submode C. I was on T/R=15sec and left
it there so the Tx Freq box turned red, no surprise
Hi Neil
Sure..
What do you prefer Word.doc or .txt file or ??
From: Neil Zampella
Reply-To: WSJT software development
Date: Sunday, February 28, 2021 at 7:41 AM
To:
Subject: Re: [wsjt-devel] Crash during QSO
David,
is it possible to send this as an attachment, rather than a 'cut
David,
is it possible to send this as an attachment, rather than a 'cut and
paste' into an email?
Thanks,
Neil, KN3ILZ
On 2/28/2021 7:23 AM, David Schmocker wrote:
Sending JA7QVI KJ9I R-24.
Awaiting RRR SH message (crash at start of Tx minute)..
On 28/02/2021 13:12, David Schmocker wrote:
Process: wsjtx [668]
Path: /Applications/wsjtx.app/Contents/MacOS/wsjtx
Identifier: org.k1jt.wsjtx
Version: v2.4.0 (2.4.0)
Code Type: X86-64 (Native)
Parent Process: bash [416]
FWIW ... you should have a saved audio file timestamped for the times
the program crashed.I would zip them up and be ready to email to the
developers as they would give more information to the developers, than
the generic Windows information.
Neil, KN3ILZ
On 1/7/2020 4:11 PM, Jari A wrote:
New crash, during contest
Problem signature:
Problem Event Name: APPCRASH
Application Name: wsjtx.exe
Application Version: 0.0.0.0
Application Timestamp: 5ddd4628
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.24540
Fault Module Timestamp: 5ddf3f5f
Exception Code:
Hi Tom,
WSJT-X 2.1.2, running VHF contest on FT8, 12 qsos previously and qso #13
cause the crash.
After crash, normal windows software close error window with option to look
for web solution. Could not do else than click to close.
While typing this, WSJT-X crash again.
No error messages, but
Jari
What version of wsjt-X?, what were you doing at the time? - ft8 / ft4?
Will need a little more info rather than just the generic windows error.
Any wsjt error messages?
Tom
--
73’s
Tom
GM8MJV (IO85)
On 7 Jan 2020, at 20:11, Jari A wrote:
> Problem signature:
> Problem Event
Problem signature:
Problem Event Name: APPCRASH
Application Name: wsjtx.exe
Application Version: 0.0.0.0
Application Timestamp: 5ddd4628
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.24540
Fault Module Timestamp: 5ddf3f5f
Exception Code: c005
Exception Offset:
Mike,
thanks for the quick response. I will see if I can squeeze some time in
between the inlaws visiting, turkey and everything else that needs to be
done for the next few days :) I'll let you know how it goes.
Tanks again,
Karl Heinz - K5KHK
Karl Heinz Kremer
PDF Acrobatics Without a Net
PDF
Karl...download the latest hamlib from my fork. Compile it and use rigctld to
test and generate debug.
https://github.com/mdblack98/Hamlib.git
rigctld -m 122 -r /dev/ttyx -s 19200 -v -Z > com port and baud
to suit your setup.
Change WSJT-X to use "Hamlib NET rigctl" and the Test button
On 27/11/2019 16:59, Bill Somerville wrote:
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
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
... one more thing: When wsjt-x comes up (before the crash), the frequency
on the radio gets changed by 50Hz up. So if I have e.g. 7074 dialed in, and
start the application, I end up with 7074.050 - but then when I manually
change the frequency (or test the CAT connection), the software crashes.
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
Hi Karl Heinz,
that stack trace you gave above shows an invalid pointer passed to the C
library free() function. There is only one free() call in the routine
that called it and the code looks fine to me, a C-string pointer
returned by strdup() is being freed and that's fine. I would guess
I retested with version 2.1.1 and 2.1.2 and I am still getting crashes
using the flrig interface to my FT857.
Again, if somebody could provide some pointers about how to create a debug
build that I can step through, I would try to narrow down the problem. I
found information about how to create a
On Sun, Nov 24, 2019 at 6:09 PM Karl Heinz Kremer wrote:
> [ ... ] I am using wsjt-x 2.0.1 on a Raspberry Pi 4
>
My fingers were a bit faster than the brain, I am of course using version
2.1.0 - sorry about that.
___
wsjt-devel mailing list
It looks like I am running into the same crash. I am using wsjt-x 2.0.1 on
a Raspberry Pi 4. I first installed the available package from the web
site, and experienced a crash. Having done seen this before, I assumed that
there probably was something incompatible with the latest Buster software
I just started a new INI file and it's working fine now.Was hoping you could
duplicate the problem...but guess not.
Since I'm not building WSJT-X anymore I don't have a debug version to figure
out what it's doing.
Mike
On Wednesday, November 13, 2019, 11:58:07 AM CST, Bill Somerville
On 13/11/2019 17:37, Black Michael via wsjt-devel wrote:
WSJT-X decided to die this morning when I was doing some frequency
calibration testing.
While idling it crashed and would not restart.
The WSJT-X.ini file in this link does not allow WSJT-X.ini to start --
it crashes soon after startup.
WSJT-X decided to die this morning when I was doing some frequency calibration
testing.While idling it crashed and would not restart.
The WSJT-X.ini file in this link does not allow WSJT-X.ini to start -- it
crashes soon after startup.
https://www.dropbox.com/s/1w5imlr2ym2v29z/wsjt-x.ini?dl=0
to the Qt5Core
code.
Makes me wish I had my Windows Mobile debugging setup.
Rick/WK1P
From: Jari A
Sent: Friday, August 16, 2019 5:36:07 AM
To: WSJT software development
Subject: [wsjt-devel] Crash report
Win 7 pro 64 bit;
WSJT-X started and being MSK144
On 16/08/2019 10:36, Jari A wrote:
Win 7 pro 64 bit;
WSJT-X started and being MSK144, - 50.280
Change manually qrg on radio to 50.313 and got FT8 signal to waterfall.
Changing mode to FT8 from MSK144, cause crash. Shut WSJT-X and
restart, got again signal from rx, change mode to FT8 and
Win 7 pro 64 bit;
WSJT-X started and being MSK144, - 50.280
Change manually qrg on radio to 50.313 and got FT8 signal to waterfall.
Changing mode to FT8 from MSK144, cause crash. Shut WSJT-X and restart, got
again signal from rx, change mode to FT8 and crash.
Wait till rx signal end, restart
Jari --
Please click on "Read Before Download" here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
... which will take you here:
http://physics.princeton.edu/pulsar/k1jt/Reported_bugs.txt
There is no need to provide further feedback on any of the known issues
in WSJT-X 2.1.0-rc5 that
Crash:
Win 7 pro 64-bit
M0FOX did CQ on 20m FT4 and I return to him several times and small error
window open in the middle of tx sequence with:
Running: D:\radio\HAM\Datamode\WSJT-X_210_RC5\wsjtx\bin\jt9 -s WSJT-X -w 1
-m 3 -e D:\radio\HAM\Datamode\WSJT-X_210_RC5\wsjtx\bin -a
On 12/17/18 11:06 AM, Claude Frantz wrote:
Hi all,
I have recompiled the package, changing from the RELEASE mode, in cmake,
to DEBUG.
I have done: Help --> download samples --> Refresh
Now, the crash occurs when: Help --> download samples
The gdb log is attached as file.
Best wishes,
Hi all,
I have done: Help --> download samples --> Refresh
Resulting in the attached output when using gdb, then bt.
Fedora 28:
Linux 4.19.9-250.vanilla.knurd.1.fc28.i686
Thread 1 "wsjtx" received signal SIGSEGV, Segmentation fault.
0xb73fa007 in QWidgetPrivate::init(QWidget*, QFlags) ()
On 11/19/2018 6:31 PM, ZL3GAV wrote:
Hi
Also, seeing this.
On first log attempt in the mock contest, WSJTx crashes, no error message.
Windows 64 Pro, ver1803 Build 17134.407
Seeing exactly this problem, too. Win10 Pro 64.
Dana
K6JQ
73
Gavin
ZL3GAV
I created an empty file, cabrillo.log, in the regular log directory.
Logging no longer causes the program to crash.
(This new file remains empty, but I think it is only filled when you choose
export?)
Mark
KC1GWX
On Mon, Nov 19, 2018 at 9:34 PM ZL3GAV wrote:
> Hi
>
>
>
> Also, seeing this.
>
Hi
Also, seeing this.
On first log attempt in the mock contest, WSJTx crashes, no error message.
Windows 64 Pro, ver1803 Build 17134.407
73
Gavin
ZL3GAV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
On 20/11/2018 02:22, K5GZR - Rick wrote:
Bill,
Start WSJT-X with RU mode enabled.
Then without doing anything else, click on Log QSO, then OK.
WSJT-X aborts… no error messages.
Rick – K5GZR
Hi Rick,
thanks for the recipe but it is not that simple. It works for me. Still
trying to work
Bill,
Start WSJT-X with RU mode enabled.
Then without doing anything else, click on Log QSO, then OK.
WSJT-X aborts. no error messages.
Rick - K5GZR
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
OK it is solved (for me),
it happens only when besides the WSJT-X instancea FT8CALL instance is
running. Starting FT8CALL causes, that decoding procedure still active
in the WSJT-X. It happens only if the WSJT-X was started before FT8CALL.
If the FT2CALL started as first, everything is
Hello group,
just one observation.
There on 7078 kHz and 14078 kHz are two active protocols, the new 77
bit FT8 and FT8CALL protocol.
The are off course not compatible.
If there is a FT8CALL activity on the frequency, WSJT-X v2 -rc1
starting decode the signals
and the DECODE button
I'm also encountering a crash (to desktop) when trying to use MSK144 on
build 7005 (clean build from svn), at the point where it attempts to
switch to TX. Everything else (e.g. the other modes) work fine.
Windows 10 Pro.
Regards, Mark
On 06/08/2016 07:47, Claude Frantz wrote:
> On 08/05/2016
On 08/05/2016 09:06 PM, Steven Franke wrote:
Hi Steve,
>> I have installed from source using 32 bit Fedora 24. I have a
>> directory share/wsjtx/JPLEPH in the install directory, but it is
>> empty. In the directory lib/ldpc/peg/ in the source working
>> directory, I can find:
>
> JPLEPH is a
Hi Claude,
> I have installed from source using 32 bit Fedora 24. I have a directory
> share/wsjtx/JPLEPH in the install directory, but it is empty. In the
> directory lib/ldpc/peg/ in the source working directory, I can find:
JPLEPH is a file, not a directory. Are you installing version 1.7
On 08/05/2016 12:40 AM, Steven Franke wrote:
Hi Steven,
> I suspect that there is an issue associated with not finding new files that
> define the LDPC code that is used for the short 20ms messages. Here’s a list
> of the files that I have in the wsjtx.app/Contents/Resources/data folder:
>
>
Rebuilt and included the listed files. Now appears to function correctly.
More learning for me!
George J Molnar
KF2T | AFA9GM
Twitter: @GJMolnar
SUPPORT HR-1301 & S-1685
http://www.arrl.org/amateur-radio-parity-act
> On Aug 4, 2016, at 16:04, Steven Franke wrote:
>
That’s not right.
Are you running the app from the wsjtx/install directory? At least, JPLEPH and
the peg-128 files should be present.
Please make sure that you are running the app from the install directory and
not from the build directory.
Steve k9an
> On Aug 4, 2016, at 5:55 PM, George
George --
You are building the program yourself, so you need to do some diagnosis
yourself when you find a problem.
Some things that would be installed automatically from the distribution
package may not be in the correct place after your builds.
If I infer correctly what you must be doing,
I do not see any of these files in the app.
George J Molnar
KF2T | AFA9GM
Twitter: @GJMolnar
SUPPORT HR-1301 & S-1685
http://www.arrl.org/amateur-radio-parity-act
> On Aug 4, 2016, at 15:40, Steven Franke wrote:
>
> George -
>
> I suspect that there is an issue
George --
I can't test in OS X, so in principle your reports could be especially
useful.
You are building the program yourself. For diagnostic purposes you
should build the "Debug" version, not the "Release" version. Can you
start it from a command-prompt window, or run it under gdb? That
George -
I suspect that there is an issue associated with not finding new files that
define the LDPC code that is used for the short 20ms messages. Here’s a list of
the files that I have in the wsjtx.app/Contents/Resources/data folder:
JPLEPH
peg-128-80-reg3.gen
Follow up on MSK144 — the crash seems to happen after the first full (15 sec in
my test so far) cycle. The decode indicator changes color, and the app dies.
Hope that helps
George J Molnar
KF2T | AFA9GM
Twitter: @GJMolnar
SUPPORT HR-1301 & S-1685
http://www.arrl.org/amateur-radio-parity-act
Hi George -
I just made a change to address an issue that I found on OS X. You might try it
to see if it fixes your problem.
Steve k9an
> On Aug 4, 2016, at 4:51 PM, George J Molnar wrote:
>
> Dev 7002 under Mac OSX 10.11.6
>
> Having trouble with crashes in MSK144 - it
Dev 7002 under Mac OSX 10.11.6Having trouble with crashes in MSK144 - it loads, but quickly crashes. Log file attached.
George J MolnarKF2T | AFA9GMTwitter: @GJMolnarSUPPORT HR-1301 & S-1685http://www.arrl.org/amateur-radio-parity-act
{\rtf1\ansi\ansicpg1252\cocoartf1404\cocoasubrtf470
Attemptimg to play with jtmsk here using r5824.
I am seeing the following:
$ ./wsjtx
At line 65 of file /home/radio/Builds/wsjtx_exp/lib/jtmsk.f90
Fortran runtime error: Index '-8543' of dimension 1 of array 'c' outside of
expected range (1:524288)
Segmentation fault (core dumped)
Also, the
Hi Steve,
Thanks for the bug report. Were you running with T/R sequence lebngth
30 s? I think there are problems there. Try setting T/R = 15 s, which
is what everyone is using. I will trace the problem.
-- Joe
On 8/29/2015 8:59 AM, Steven Franke wrote:
Attemptimg to play with
Steve --
No apparent problem here when monitoring a birdie. Does it die when
attempting to decode, at the end of a sequence? If you hace checked
Save all and re-open the saved file, does that crash the program? If
so, could you send me the file?
-- Joe
On 8/29/2015 10:29 AM,
Hi Bill, Steve, and all,
On 8/29/2015 9:44 AM, Bill Somerville wrote:
On 29/08/2015 13:59, Steven Franke wrote:
Hi Steve,
Attemptimg to play with jtmsk here using r5824.
I am seeing the following:
$ ./wsjtx
At line 65 of file /home/radio/Builds/wsjtx_exp/lib/jtmsk.f90
Fortran runtime
Steve --
On 8/29/2015 10:29 AM, Steven Franke wrote:
OK, I spoke too soon. Running with 15s T/R sequence. Seems to run OK when the
input is “pure” noise - but I can make it crash within seconds if I tune to
or tune slowly through a birdie.
That may be a different problem. I will
OK, I spoke too soon. Running with 15s T/R sequence. Seems to run OK when the
input is “pure” noise - but I can make it crash within seconds if I tune to or
tune slowly through a birdie.
Steve k9an
On Aug 29, 2015, at 2:22 PM, Steven Franke s.j.fra...@icloud.com wrote:
T/R sequence length
Steve --
I think the problem is related to T/R =30 s sequences.
For frequency selection: you need to explicitly enter one or more
frequencies for JTMSK mode.
-- Joe
On 8/29/2015 9:52 AM, Steven Franke wrote:
Thanks Bill. I hadn’t thought through the frequency selection issue.
A bit
It still crashes on the file that I sent to you Joe…
Steve k9an
On Aug 29, 2015, at 3:35 PM, Joe Taylor j...@princeton.edu wrote:
Hi Bill, Steve, and all,
On 8/29/2015 9:44 AM, Bill Somerville wrote:
On 29/08/2015 13:59, Steven Franke wrote:
Hi Steve,
Attemptimg to play with jtmsk here
Steve --
I didn't get a file from you, today???
-- Joe
On 8/29/2015 1:02 PM, Steven Franke wrote:
It still crashes on the file that I sent to you Joe…
Steve k9an
On Aug 29, 2015, at 3:35 PM, Joe Taylorj...@princeton.edu wrote:
Hi Bill, Steve, and all,
On 8/29/2015 9:44 AM, Bill
62 matches
Mail list logo