To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=47132


User mhu changed the following:

                  What    |Old value                 |New value
================================================================================
                    Status|RESOLVED                  |VERIFIED
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Fri Apr 28 05:01:45 -0700 
2006 -------
This has now been verified (in a slightly modified revision, see below) on an
Athlon 64 system, running Fedora Core 5 with SELinux enabled (Sun internal: 
of-1).

The initial change in /bridges/source/cpp_uno/shared/vtablefactory.cxx had to be
adapted again, similiar to what cmc proposed recently: an mmap (PROT_READ |
PROT_WRITE | PROT_EXEC) will fail with "allow_execmem = false". Anon memory
needs to be mmap()'d w/o PROT_EXEC, and lateron mprotected() to become 
executable.

The apparently most clean solution (memory protection wise) is in cmc's 2nd
patch (of Mar 20): allocate writeable memory, assemble the code snippets, then
mprotect() to PROT_READ+PROT_EXEC.

But, even that may fail when "allow_execmod = false" which would let the
mprotect() call fail as well (though I haven't tested this myself).

Anyway, the fix is verified to work under "allow_execmem = false" => verified.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to