Welcome to the Bug Tracking System for the Win-Test contest logger. Things to note :
- Always perform a search on both open and closed tasks before opening a new one. Your bug might already have been reported.
- Only one bug per task
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 crashAttached to Project— Win-Test
(WT 3.18, perhaps 3.19 as well)
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?
# ChildEBP RetAddr Args to Child
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?
Waiting for more reports. Fixes introduced in 3.20.0