On Saturday 22 April 2006 08:38, Marcus Meissner wrote: [snip]
Well, in your case it seems to be the main executable, since it faults at its very first instruction.
Maybe I'm just misunderstanding what you're saying here, but the problem is _not_ with the application I am attempting to run. It works flawlessly with an x86-64 kernel with noexec32=off, or 2.6.14.7 (where this is the default).
[alistair] 11:17 [~/.wine/drive_c/Program Files/Warcraft III] wine war3.exe -opengl wine: Unhandled page fault on write access to 0x00495000 at address 0x495000 (thread 0009), starting debugger...
=>1 0x00495000 EntryPoint in war3 (0x00495000) 2 0xf7f763ab wine_switch_to_stack+0x17 in libwine.so.1 (0xf7f763ab) 0x00495000 EntryPoint in war3: pushl %eax
Please run with: WINEDEBUG=+virtual wine war3.exe -opengl
And look for the virtual entries in the vicinity of 495000.
Can't see anything obvious. Here's the entire trace:
http://devzero.co.uk/~alistair/wine/virtual.log