Win-Test

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 #188 — CLEARLOGNOW or REOPENNOW often causes crash

Attached to Project— Win-Test
Opened by Robert A. Wilson (N6TV) - Saturday, 26 Jan 2008, 12:14am
Bug Report
General
Unconfirmed
No-one
All
Medium
Normal
WT-3.1.x
Undecided
0% complete

(WT 3.18, perhaps 3.19 as well)

  1. Create an empty Win-Test file
  2. Enter some QSOs
  3. Type REOPENNOW or CLEARLOGNOW
  4. Bug - WinTest will often crash at this point and produced a core dump. It doesn\'t happen every time.

See dump file N6TVCoredump.zip emailed 22 November 2007.

Analysis of dump file shows a access violation at offset +10E7 in a routine that takes \"CLEARLOGNOW\" as one of its string agruments. ebp is bad. Stack overflow? Memory corruption?

Details below: # ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong. 00 0012fcac 00465547 00000001 0190f6ec 00000000 wt+0x66637 01 0012fcc8 005379c4 0000000d 00000000 00f62e48 wt+0x65547 02 0012fcf0 00536c04 0000000d 00000000 00f62e48 wt+0x1379c4 03 0012fd08 0057817a 0000000d 00000001 0000001c wt+0x136c04 04 0012fd38 77e2e117 0016047c 0012fd7c 77e1479a wt+0x17817a 05 0012fd5c 77e3a454 001b0486 00000363 00000001 USER32!ButtonWndProcA+0x5a (FPO: [Non-Fpo]) 06 0012fd88 00577d0f 00000102 0000000d 005be190 USER32!UserCallWinProc+0x18 07 0012fdac 00576b5d 00000102 0000000d 001c0001 wt+0x177d0f 08 0012fe0c 00576e13 00f62e48 00190346 00000102 wt+0x176b5d 09 0012fe28 77e3a454 00190346 00000102 0000000d wt+0x176e13 0a 0012fe48 77e14605 00576de8 00190346 00000102 USER32!UserCallWinProc+0x18 0b 0012fed4 77e15b77 00609490 00000001 0057b680 USER32!DispatchMessageWorker+0x2e4 (FPO: [Non-Fpo]) 0c 0012fee0 0057b680 00609490 005bdd80 00609460 USER32!DispatchMessageA+0xb (FPO: [1,0,0]) 0d 00000000 00000000 00000000 00000000 00000000 wt+0x17b680

The caller called wt+0x65550 with one of the arguments the string \"CLEARLOGNOW\"

0190f6ec C L E A R L O G N O W .

Then later in this function at wt+0x66637 (offset 0x10E7), we get an access violation.

If you can send me the symbol file (.sym) for WT 3.18.0, maybe the context will become more clear.

Looks like WT got an access violation because ebp was messed up:

(480.678): Access violation - code c0000005 (!!! second chance !!!) eax=00000000 ebx=00000000 ecx=0012fc43 edx=00000043 esi=005eee60 edi=0000000d eip=00466637 esp=0012fc80 ebp=01908970 iopl=0 nv up ei pl zr na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246 *** WARNING: Unable to verify checksum for wt.exe *** ERROR: Module load completed but symbols could not be loaded for wt.exe wt+0x66637: 00466637 8a4563 mov al,byte ptr [ebp+63h] ss:0023:019089d3=??

Here\'s the context of the failing instruction:

00466611 8aca mov cl,dl 00466613 3a5601 cmp dl,byte ptr [esi+1] 00466616 750e jne wt+0x66626 (00466626) 00466618 83c002 add eax,2 0046661b 83c602 add esi,2 0046661e 84c9 test cl,cl 00466620 75e0 jne wt+0x66602 (00466602) 00466622 33c0 xor eax,eax 00466624 eb05 jmp wt+0x6662b (0046662b) 00466626 1bc0 sbb eax,eax 00466628 83d8ff sbb eax,0FFFFFFFFh 0046662b 3bc3 cmp eax,ebx 0046662d 7504 jne wt+0x66633 (00466633) 0046662f c6456300 mov byte ptr [ebp+63h],0 00466633 33c0 xor eax,eax 00466635 6aff push 0FFFFFFFFh 00466637 8a4563 mov al,byte ptr [ebp+63h] ss:0023:019089d3=??

And the register values at the time of the crash:

eax 0 ebx 0 ecx 12fc43 edx 43 ebp 1908970 edx 43

Looks like the stack pointer (base pointer ebp) got messed up?

This task depends upon

This task blocks these from closing

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

Comment by F6FVY - Friday, 30 May 2008, 3:09pm

Waiting for more reports. Fixes introduced in 3.20.0