http://bugs.winehq.org/show_bug.cgi?id=9975
--- Comment #7 from Juan Lang juan_lang@yahoo.com 2007-10-10 12:15:26 --- If you mean errors like: 0009:CALL MFC42.765(<unknown, check return>(0x110000,00000002,00000040): returning 0x1d633f8 ) ret=00401730 0009:RET MFC42.765() retval=00000000 ret=00401730
Those are a red herring. It just means that the parameters to the function are unknown by the relay/snoop mechanism until the function returns because of the calling convention. (If you don't know what that means, just ignore.)
The problem is an uninitialized variable somewhere or another. From the log, the first seh entry is: 0009:trace:seh:raise_exception code=c0000005 flags=0 addr=0x4383e0 0009:trace:seh:raise_exception info[0]=00000000 0009:trace:seh:raise_exception info[1]=55555555 0009:trace:seh:raise_exception eax=00000000 ebx=00000000 ecx=55555555 edx=00000029 esi=01d5f5f4 edi=7e77e8b0
c0000005 is an access violation, and ecx has the bogus value: 0x55555555. Microsoft uses that value for uninitialized variables in debug versions of their libraries to help you catch bugs. This could well be an app bug that happens not to occur on Windows.