http://bugs.winehq.org/show_bug.cgi?id=25206
--- Comment #71 from rawfox rawfox@freenet.de 2011-01-26 16:29:20 CST --- (In reply to comment #70)
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.
With the +relay option im getting a timeout while the char is loading. The messages, typed to console need too mutch time, the program executes too slow. I piped that overhelming message salad to a file, bigger then 1GB. Now i havnt made it yet, to copy some pages before and after the crash because the file is so damn huge, im still working on that.
I was not able to bind any debugging to the AwesomiumProcess.exe, how can i do that ?
Btw, i used a clean wineprefix while trying this.
Do you use your exception solution in your RtlCaptureStackackTrace ? Or do you also just return 0; ?
Ill make some futher tests with AwesomiumGL
cheers ^^