http://bugs.winehq.org/show_bug.cgi?id=22429
--- Comment #11 from Juan Lang juan_lang@yahoo.com 2010-04-26 10:35:03 ---
From your log file, this is curious:
0009:Call KERNEL32.SetLastError(0000003b) ret=003e83d0 0009:Ret KERNEL32.SetLastError() retval=0000003b ret=003e83d0 0009:Call ntdll.NtQueryInformationProcess(ffffffff,0000000c,0033e4f0,00000004,00000000) ret=003bab33 0009:trace:ntdll:NtQueryInformationProcess (0xffffffff,0x0000000c,0x33e4f0,0x00000004,(nil)) 0009:Ret ntdll.NtQueryInformationProcess() retval=00000000 ret=003bab33 0009:Call KERNEL32.GetLastError() ret=003e8418 0009:Ret KERNEL32.GetLastError() retval=0000003b ret=003e8418 (snip) 0009:Call ntdll.NtTerminateProcess(ffffffff,ffffffff) ret=003ba997
The process is setting the last error to 0x3b (59, ERROR_UNEXP_NET_ERR) before calling NtQueryInformationProcess. NtQueryInformationProcess succeeds, but the program is calling GetLastError and killing the process anyway. Perhaps it expects the last error to be cleared? I'll attach a new patch in a sec.