http://bugs.winehq.org/show_bug.cgi?id=29168
--- Comment #83 from Xolotl Loki xoloki@gmail.com 2012-01-09 15:36:53 CST --- (In reply to comment #82)
Thanks for looking at this Jeremy; it's good to have skilled eyes in addition to the internet hordes.
I sacrificed my swap partition to install windows a couple of weeks ago, and I've been playing in XP since. I noticed that I often see aborts when running under XP; windows pulls me back to the desktop, with an error dialog saying something like "ABORT: NULL pointer at socket.c/385". So it's entirely possible that TOR itself has bugs in its network code path, and it's subtle differences in error paths that's causing the troubles.
I'm going to try testing with Jeremy's +seh debug flag. I suspect that the thread which is reading the socket on port 8995 dies after recving the 22 byte packet, before it can send the login data. Hopefully this death will be related to some wine function.
Does anyone have any other suggestions?