http://bugs.winehq.org/show_bug.cgi?id=15485
William Waghorn willw@litany.me.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |willw@litany.me.uk
--- Comment #37 from William Waghorn willw@litany.me.uk 2008-10-25 22:00:01 --- Previous posts have inspired me to try a bit of amateur debugging...
0x1004e23e: movl 0x100c091c,%eax 0x1004e243: movl 0x0(%eax),%eax 0x1004e245: cmpl %ebx,0x6c(%eax)
Then,
Wine-dbg>x /x 0x100c091c 00693300
Wine-dbg>watch *0x693300 Watchpoint 1 at 0x00693300 _PyThreadState_Current in python25
The Page Fault itself is happening outside of Wine. Execution flow leaves Wine via a message callback for WM_ACTIVATEAPP.
The location 0x693300 changes continuously, and may often contain zero. Not surprising if this is the address of _PyThreadState_Current.
So, evidence to date suggests that Eve's WM_ACTIVATEAPP handler is querying state from Python. The method it is using is somehow bypassing whatever mechanism should protect the _PyThreadState_Current value.