[Bug 4619] Warcraft III infinite timeout when trying to connect a badly hosted game on battle.net

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=4619

------- Additional Comments From [e-mail]  2006-25-07 08:21 -------
Created an attachment (id=3035)
 --> (http://bugs.winehq.org/attachment.cgi?id=3035&action=view)
backtraces of the threads

How to produce such backtraces:
- start Warcraft Frozen Throne with winedbg instead of wine
you will get a console output like this:
...
2163	    status = entry( peb );
Wine-dbg>
- enter "cont" in oder to continue starting warcraft 3
- join a game which is hosted by someone with closed ports
- change to console (e.g. with [alt]+[tab])
- press [str]+c
- you should get again:
Wine-dbg>
- type "info process", you should get something like this:
 pid	  threads  parent   executable (all id:s are in hex)
 00000013 12	   0000000e 'war3.exe'
 00000010 1	   0000000e 'explorer.exe'
Wine-dbg>
- enter "attach 0x" plus the process id of war3.exe. In the given example you
would type: "attach 0x13"
you will get a output similar to this:
0xffffe40e: jmp 0xffffe403
Wine-dbg>
- type "info thread"
you should get the thread IDs of each thread like this:
00000013 (D) C:\Programme\Warcraft III\war3.exe
    00000026   15 <==
    00000023    0
    00000021    0
    00000020    0
    0000001f    0
    0000001e    0
    0000001d    0
    0000001c   15
    00000019   15
    00000017    0
    00000016    1
    00000014    0
00000010
    00000011    0
-For each thread ID of the war3.exe process you type "bt 0x" + the ID of the
thread.
The command for the first thread of the example would look like this: "bt 0x26"

- save now the produced log.
- you may continue playing(= seeing the blocked interface) with "cont" if you
want.