http://bugs.winehq.org/show_bug.cgi?id=25206
--- Comment #70 from Janne Hakonen joyer83@live.fi 2011-01-25 16:13:30 CST --- (In reply to comment #69)
Created an attachment (id=32991)
--> (http://bugs.winehq.org/attachment.cgi?id=32991) [details]
AO sessionlog until wine error window comes up
WINEDEBUG=+seg,+tid,+process
Loading AO, logging in, pressing the shop button, shop crashes then.
Looking at the log, thread 1c, which was the one that had crashed.
At first, there were quite a lot access violation (code=c0000005) exceptions at address 0x6ff3602b, but those were handled OK.
There is also code=406d1388 exception which basically just gives the thread a name. A debugger can catch it if needed. That was handled OK too.
Then the exception that crashed the application was again an access violation at different address 0x108a8f64, trying to read from memory address 0x00000000, this time the exception was not caught and it killed the app.
Next course of actions could be to add +relay to the WINEDEBUG to get more debug information. Another thing to try, could be to attach the debugger to AwesomiumProcess.exe when it crashes and using disassembler to check what that address 0x108a8f64 contains.