http://bugs.winehq.org/show_bug.cgi?id=4790
------- Additional Comments From rmh@aybabtu.com 2007-07-03 16:56 -------
Urgh. +relay seems to indicate that CPUID was used just before the exception happened. Earlier I verified that the code is testing for SSE and SSE2 flags (although disabling these checks didn't avoid the FPE). This makes sense, but contradicts my former supposition. I'm not sure about anything now (maybe this FPE is just the wrong thing to look at?) :-(
0009:Call kernel32.MultiByteToWideChar(00000000,00000000,008c99a0 "AuthenticAMD",ffffffff,010a1150,0000000c) ret=00798320 0009:Ret kernel32.MultiByteToWideChar() retval=00000000 ret=00798320 0009:Call ntdll.RtlAllocateHeap(010a0000,00000000,00000010) ret=0082a2a9 0009:Ret ntdll.RtlAllocateHeap() retval=010a1178 ret=0082a2a9 0009:Call kernel32.WideCharToMultiByte(00000000,00000000,010a1150 L"AuthenticAMD",ffffffff,010a1178,0000000c,00000000,00000000) ret=0079796e 0009:Ret kernel32.WideCharToMultiByte() retval=00000000 ret=0079796e err:seh:fpe_handler Got unexpected trap 19