http://bugs.winehq.org/show_bug.cgi?id=29448
--- Comment #7 from Juan Lang juan.lang@gmail.com 2011-12-30 18:19:30 CST --- Seems somewhat like a heap corruption, doesn't it? What's up with the access violations prior to WinVerifyTrust? e.g.:
0042:Ret KERNEL32.InterlockedDecrement() retval=00000002 ret=00ad2509 0042:trace:seh:raise_exception code=c0000005 flags=0 addr=0xaf1bf2 ip=00af1bf2 tid=0042 0042:trace:seh:raise_exception info[0]=00000001 0042:trace:seh:raise_exception info[1]=00000000 0042:trace:seh:raise_exception eax=00000000 ebx=00dac4d0 ecx=00dac9bc edx=00000001 esi=00137f11 edi=00401004 0042:trace:seh:raise_exception ebp=0033fd34 esp=0033fd1c cs=0073 ds=007b es=007b fs=0033 gs=003b flags=00210246 0042:trace:seh:call_vectored_handlers calling handler at 0x7ec08ee0 code=c0000005 flags=0 0042:trace:seh:call_vectored_handlers handler at 0x7ec08ee0 returned 0 0042:trace:seh:call_stack_handlers calling handler at 0xaf1bf4 code=c0000005 flags=0 0042:trace:seh:call_stack_handlers handler at 0xaf1bf4 returned 0 0042:Call KERNEL32.InterlockedDecrement(00daca2c) ret=00ad2499
The stack overflow doesn't appear in your +relay et al log:
0042:fixme:wintrust:WinVerifyTrust unimplemented for 11655724 0042:trace:wintrust:WinVerifyTrust returning 00000000 0042:Ret wintrust.WinVerifyTrust() retval=00000000 ret=00b1d98c
So I think that's a red herring. I think you want to look for memory corruption.