On Saturday 22 April 2006 02:53, Alistair John Strachan wrote:
> > > Alistair, if you can do a "git bisect" on this one, that would help.
> >
> > If noexec32=off doesn't help please do.
> > If noexec32 helps then it's likely a wine bug for using the wrong
> > protections.
>
> [alistair] 01:52 [~] uname -rm
> 2.6.17-rc2 x86_64
>
> [alistair] 01:52 [~] cat /proc/cmdline
> vga=794 root=/dev/sda1 quiet noexec32=off
>
> [alistair] 01:51 [~/.wine/drive_c/Program Files/Warcraft III] wine
> war3.exe -opengl
> err:ole:CoCreateInstance apartment not initialised
> fixme:advapi:SetSecurityInfo stub
>
> Aaand wine suddenly starts working again.
Ok. There is a way to change this at runtime for individual
processes too (using personality), but most distros seem
to miss the user tools for that so far.
> Looks like a bug in WINE; is there
> any additional information required before I can file a bug report on this
> one? Thanks.
They probably forget to set PROT_EXEC in either mprotect or mmap somewhere.
You can check in /proc/*/maps which mapping contains the address it is faulting
on and then try to find where it is allocated or mprotect'ed.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
