To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=52428
                  Issue #:|52428
                  Summary:|bridges::cpp_uno::shared::VtableFactory::createBlock
                          |not guaranteed PROT_EXEC
                Component:|udk
                  Version:|680m119
                 Platform:|All
                      URL:|
               OS/Version:|Linux
                   Status:|NEW
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|PATCH
                 Priority:|P3
             Subcomponent:|code
              Assigned to:|kr
              Reported by:|cmc





------- Additional comments from [EMAIL PROTECTED] Mon Jul 25 01:12:19 -0700 
2005 -------
Basically I would like OOo to be marked as supporting execshield, this is
currently not the case because libgcc3_uno.so is marked automatically as
requiring executable stack. This is because there is an assembly file dependancy
which automatically makes the toolchain mark the resulting .so as needing
exectable stack. Marking this as not requiring stack surprisingly caused remote
bridges to fail, e.g. pyuno. 

Examining a bit more closely I tracked it down to...

bridges::cpp_uno::shared::VtableFactory::createBlock{
  char * block = new char[...
}

where block is expected to be executable memory, under execshield this is not
the case. If marked as executable after the fact with the attached demo hack, or
if created initially through rtlAlloc which sets as PROT_EXEC then there are no
problems. Presumably the best solution (if one is desired) would be to refactor
in terms on rtl_Alloc instead of new for the GuardedArray and friends.

I initially thought that we actually globally set new_handler to use the sal
allocater, which would have had the desired results, but this seems not to be
the case.

---------------------------------------------------------------------
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