http://bugs.winehq.org/show_bug.cgi?id=25206
--- Comment #67 from rawfox rawfox@freenet.de 2011-01-24 17:50:37 CST --- (In reply to comment #66)
Rawfox, your problem seems similar to what Lupusceleri has at AO's forums. Can you check my answers to that at here: http://forums.anarchy-online.com/showpost.php?p=5921532&postcount=43
And, see if those help at all?
You like to get debugger output from AwesomiumGL, no sorry, i havnt done that yet.
Some google'n on wine page fault problems made me guess problems in the multithreading code, in our case, the problem exists already -before- it enteres RtlCaptureStackBackTrace.
RtlCaptureStackBackTrace works so far, honestly i dont belive, that returning 0; fixes anything at all and i like to have that explained, kinda "pics or it didnt happen" ;)
My investigations made me learn, that while the shop window is loading, RtlCaptureStackBackTrace (modified to return 0;) is touched multible times before it chrashes and even -after- the page fault crash, it is touched again 2 times.
The function looks like this:
USHORT WINAPI RtlCaptureStackBackTrace( ULONG skip, ULONG count, PVOID *buffer, ULONG *hash ) { FIXME( "(%d, %d, %p, %p) MY_i386_1_stub!\n", skip, count, buffer, hash ); return 0;
}
Terminaloutput while pressing the shop button:
fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x33f0c4, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (5, 30, 0x29c0118, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x33f070, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (5, 30, 0x3e01a0, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x33e900, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x7bfda50, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x7bfd850, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x7bfd4d8, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (5, 30, 0x29c0228, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (5, 30, 0x3e0228, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x33e39c, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x33e474, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (5, 30, 0x3e0338, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (5, 30, 0x3e0448, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x33e544, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (5, 30, 0x3e04d0, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x33e39c, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x33e5a4, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x33e474, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x33e474, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x33f1bc, (nil)) MY_i386_1_stub! fixme:seh:RtlCaptureStackBackTrace (3, 31, 0x33e4bc, (nil)) MY_i386_1_stub! wine: Unhandled page fault on read access to 0x00000000 at address 0x108a8f64 (thread 002a), starting debugger...
At this point, the wine error window pops up.
You can see the multible functioncalls before it crashes.
Changeing the function back to its original state, has the exact same output, when i place the fixme: in there. This should be proof, that RtlCaptureStackBackTrace is -not- the problem.
I'd be happy if someone would correct me, this multithreadig stuff is far over my head ^^