From: "Leopold Toetsch" <[EMAIL PROTECTED]> > Vladimir Lipsky <[EMAIL PROTECTED]> wrote: > >> Ah, that's the reason for your bug report WRT JIT/NCI. The question is, > >> how can we detect the presence of the exec-shield patch. Your `uname -a` > >> doesn't indicate it. > > > What for? We just always do allocating memory from a JIT dedicated heap with > > execute flas set on it, no matter the presence of the exec-shield patch, > > I doubt, that my kernel has an appropriate allocation function (besides
So do I. Well, there is, of course, HeapCreate on windows but I'm afraid it marks the memory being reserved as READ & WRITE and there is no mean to pass the function any flags. > mmap() with PROT_EXEC - which isn't resizable AFAIK). Besides VirtualAlloc with PAGE_EXECUTE. As to resizing, yeah it's bad; VirtualAlloc doesn't do resing either. We will have to rewrite all the things that malloc() does with relative to resizing. Bad. Very bad. > > ... or > > OS is windows XP with service pack 2 installed, or the processor supports > > NX. > .. or that an older Win32 has the necessary system call to get > executable memory. Old windows indeferently executes data from pages not marked as EXECUTE. So there won't be any problems, at least until Microsoft decides to patch them. > leo 0x4C56
