JIT breaks on feather3

chromatic chromatic at wgz.org
Wed Dec 3 08:31:13 UTC 2008

On Tuesday 02 December 2008 22:27:15 Mark Glines wrote:

> Kevin mentioned that parrot is using mprotect() to explicitly ask glibc
> to make this memory executable.  Since it isn't, that possibly makes
> this a glibc bug.  Either way, this seems like the sort of issue which
> would keep cropping up in weird ways, unless we could detect/prevent it
> somehow.
> So, List, does anyone happen to know why processes under screen have
> non-executable stacks?  Or possibly a bash shopt or ulimit or dropped
> privilege or somesuch?

SELinux or GCC stack protection might also do this (though I'm not *sure* of 
the latter).

-- c

More information about the parrot-dev mailing list