http://bugs.winehq.org/show_bug.cgi?id=22032
--- Comment #1 from Enrico Enrico_m@gmx.de 2010-03-18 19:15:15 --- Created an attachment (id=26883) --> (http://bugs.winehq.org/attachment.cgi?id=26883) workaround to prevent the unhandled exception
some more infos:
1. If the first start of a steam app fails, it will always fail until steam is restarted. 2. If the game start succeeds (rare case), all starts will succeed until steam is restarted. 3. The unhandled exception does not occur if steam is started in winedbg, but it will occur if winedbg is attached later. I guess the real problem is during steam startup and not the app startup. 4. winedbg pointed to - GetConsoleInputExeNameA (dlls/kernel32/console.c) - GetConsoleTitleA (dlls/kernel32/console.c) - attach_process_dlls (dlls/ntdll/loader.c) after changing GetConsoleInputExeNameA and GetConsoleTitleA to simple stubs, attach_process_dlls kept popping up. Deleting the call to pthread_sigmask in attach_process_dlls fixed the unhandled exception (even if reverting GetConsoleInputExeNameA and GetConsoleTitleA).
I don't know how to really fix this bug, but I hope this maybe helps a real wine developer to investigate.
btw: many other steam user have had the unhandled exception too, but they fixed it by disabling the steam in-game overlay. This was not a big issue, because the in-game overlay did not work until know (you just need a gcc newer than 4.4.3, I just build one from svn).