http://bugs.winehq.org/show_bug.cgi?id=21809
--- Comment #8 from Roderick Colenbrander thunderbird2k@gmail.com 2010-03-01 05:34:45 --- Created an attachment (id=26558) --> (http://bugs.winehq.org/attachment.cgi?id=26558) Log file
I'm also looking at the crash right now. With some difficulty and some late-tracing hacks, I managed to record a short +all log (I activated the +all at the moment you hit the button). This is my log.
The crash occurs in battle.net.dll which is also full of debugging traps. At the end of the log you see some stack corruption. Before that point you see CreateToolhelp32Snapshot + Process32FirstW/Process32NextW calls.
I'm not sure why those functions are called. It can either be because there was a crash before those calls (perhaps something related to the memcpy/memset calls) and that these calls are part of debugging related calls (note that also CheckRemoteDebuggerPresent is called at that point). It can also be that these calls are being made to prevent reverse engineering of battle.net.