Re: JIT On Win32: A possible future issue

2003-12-23 Thread Vladimir Lipsky
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 alwa

Re: JIT On Win32: A possible future issue

2003-12-23 Thread Leopold Toetsch
Peter Gibbs <[EMAIL PROTECTED]> wrote: > Leopold Toetsch wrote: >> So we need: >> >> 1) a config test/option/whatever (e.g. mallocing some mem, fill in a >> "ret" instruction and call that. >> 2) Some means to allocate executable memory. >> >> Could you please have a look at fedora (kernel) docs?

Re: JIT On Win32: A possible future issue

2003-12-23 Thread Leopold Toetsch
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 >

Re: JIT On Win32: A possible future issue

2003-12-23 Thread Peter Gibbs
Leopold Toetsch wrote: > So we need: > > 1) a config test/option/whatever (e.g. mallocing some mem, fill in a > "ret" instruction and call that. > 2) Some means to allocate executable memory. > > Could you please have a look at fedora (kernel) docs? There are two ways to flag memory as executable

Re: JIT On Win32: A possible future issue

2003-12-23 Thread Vladimir Lipsky
> 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

Re: JIT On Win32: A possible future issue

2003-12-23 Thread Leopold Toetsch
Peter Gibbs <[EMAIL PROTECTED]> wrote: > Leopold Toetsch wrote: >> JIT code is run in malloc'ed memory (s. jit.c:1026) as well as JITted >> NCI stubs. We already have some system specific stuff for JIT (some >> architectures need a page flush before execution). >> >> So best would be to use a set

Re: JIT On Win32: A possible future issue

2003-12-23 Thread Peter Gibbs
Leopold Toetsch wrote: > JIT code is run in malloc'ed memory (s. jit.c:1026) as well as JITted > NCI stubs. We already have some system specific stuff for JIT (some > architectures need a page flush before execution). > > So best would be to use a set of spcialized function, e.g.: > - mem_alloc_ex

Re: JIT On Win32: A possible future issue

2003-12-23 Thread Leopold Toetsch
Jonathan Worthington <[EMAIL PROTECTED]> wrote: > Hi, > I was looking over the WinXP Service Pack 2 "Changes to functionality" > document, which you can get here:- > http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn > ol/winxppro/maintain/winxpsp2.asp (download availabl