for Project:

Welcome to the Bug Tracking System for the Win-Test contest logger. Things to note :

Feel free to report any bugs, however minor. To improve efficiency, please try to be as accurate as possible.

Please don't ask for feature requests here but on the mailing list.

Thanks for your help. Olivier F5MZN and Laurent F6FVY

Task #383 — WT crashes after QSO logged on VHF bands

Attached to Project— Win-Test
Opened by Sergey (ru3rq) - Sunday, 24 Jun 2018, 5:01pm
Bug Report
Current WT-4.x
0% complete

Bug was found on several different PC's OS Windows 7 32bit, Windows XP WT version 4.25...4.28 Generic VHF+Contests European V/UHF Contest

WT crashes after QSO logged on VHF bands. All QSO data are correct (CALL, number, LOC). No additional information, only OS message "wt.exe has encountered a problem and need to close." "Exception information. Code: 0xc000005"

WT 4.24 works OK.

This task depends upon

This task blocks these from closing

Comments (3) | Attachments (0) | Related Tasks (0/0) | Notifications (2) | Reminders (0) | History |

Comment by F6FVY - Sunday, 24 Jun 2018, 5:24pm

Could you be more specific ?

You get a crash EVERYTIME you enter a QSO ? Is the contest setting "European V/UHF Contest - No Mults" ?

Sorry, but I cannot reproduce the bug here :-(

Comment by Sergey - Tuesday, 26 Jun 2018, 10:46pm

I think it my fault. I use .WTS script with function wtQso:IsExchangeEmpty() which incorrectly interpreted if exchange contains two parts - RST and LOC. _ I was confused by the different behavior of 4.24 and newer versions. Please close this task.

Comment by F6FVY - Tuesday, 26 Jun 2018, 10:59pm

FYI, you can read the GridSquare field with the wtQso:GetData() API : Check the ['gridsquare'] field of the returned array. Hope this helps.