https://bugs.winehq.org/show_bug.cgi?id=29777
Timur Kristóf venemo@msn.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |venemo@msn.com
--- Comment #44 from Timur Kristóf venemo@msn.com --- I can reproduce the bug here. Tried running EVE in winedbg and I get a very similar output to what everyone else attached already.
I would guess it's some sort of memory management issue: Unhandled exception: page fault on write access to 0x00000108 in 32-bit code (0x05a59551).
But the back trace is not very helpful either: Backtrace: =>0 0x05a59551 in _gameworld (+0x1c9551) (0x0033ae6c) 1 0x0597b4ed in _gameworld (+0xeb4ec) (0x0033af24) 2 0x058aaa00 in _gameworld (+0x1a9ff) (0x0033af3c) 3 0x058b4617 in _gameworld (+0x24616) (0x0033af68) 4 0x058b47f0 in _gameworld (+0x247ef) (0x0033af78) 5 0x1e026a66 in python27 (+0x26a65) (0x28b39670)
There seems to be a python module called "_gameworld" which is called by "python27". It is unclear what exactly the thing does, it'd be more helpful if we could see further in the backtrace or know what was happening when the page fault happened.