http://bugs.winehq.org/show_bug.cgi?id=34218
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #11 from Anastasius Focht focht@gmx.net --- Hello Roland,
looks like some game with SafeDisc copy protection scheme (which should work with Wine).
+loaddll,+module channels alone are not enough to diagnose things 'offline'.
--- snip --- err:ntdll:RtlpWaitForCriticalSection section 0x39a9b8 "?" wait timed out in thread 003d, blocked by 0009, retrying (60 sec) --- snip ---
For deadlocks you have to additionally use at least 'tid' channel (thread id). If a thread died for whatever reason, holding a lock (critical section), then an exception should be seen -> 'seh' channel (exception info).
To get at least some overview without using the heavy +relay 'gun' (which interferes with certain copy protections) please generate a log as follows:
WINEDEBUG=+tid,+seh,+process,+loaddll,+module wine ./foo.exe >>log.txt 2>&1
FYI: winedbg can't be used here for dumping thread contexts from all processes.
Part of the copy protection scheme is that two game processes exist where one acts as debugger and the other is the debuggee. Winedbg can't attach to the interesting process (=debuggee), hence the error messages 'warning: could not attach to <pid>'. It's still possible do that but that requires some advanced techniques not being discussed here ;-)
Anyway, please provide the log with above debug channels.
Regards