http://bugs.winehq.org/show_bug.cgi?id=22064
--- Comment #44 from Juan Lang juan_lang@yahoo.com 2010-08-23 11:39:14 --- Okay, I had a look. I'm guessing that this will be a challenge to debug from logs. Here's the error message you pointed out before:
003c:Call KERNEL32.OutputDebugStringA(02c64250 "mg\orbitdll\ProxyConn.cpp (213): Failed while waiting for hello message, timedout = yes\n") ret=1004b68c
So, assuming that message is actually indicative of the problem, we should expect to see some sort of wait prior to this. I see lots of calls like:
002e:Ret ws2_32.WSAGetLastError() retval=00000102
0x102 is STATUS_TIMEOUT, aka WAIT_TIMEOUT. In the log there's also a: [13.365371] 002e:trace:seh:raise_exception code=c0000005 flags=0 addr=0x1001d67a ip=1001d67a tid=002e
c0000005 is a crash. Perhaps this is a red herring, but I wonder whether this crash is somewhere in a thread which should have been receiving data, which causes it never to receive it? I suspect someone willing to disassemble the app and debug the crash that way will get further with this than I.