To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=71057
------- Additional comments from [EMAIL PROTECTED] Wed Nov 1 03:06:46 -0800 2006 ------- There are at least two problems involved why certain files (executables, shared libraries) have executable stackes: 1 At least for Sun-built OOo, a rather old tool chain (including an old libc) causes many (all?) files to have executable stacks, simply because they are built with that tool chain. For libuno_sal.so.3, it has been verified that the tool chain is the only reason why that shared library has an executable stack. See issue 70840. I will verify that an OOo built using another tool chain indeed leads to a libuno_sal.so.3 without an executable stack. 2 On top of the the first problem, there are files that have an executable stack due to further problems. One such file is libgcc3_uno.so, addressed in issue 70845. Other such files have not yet been found as far as I know. However, as I wrote in issue 70840: "I assume that this libc issue causes most of the output of the scanelf call above. Once this libc issue is fixed, any remaining output of the scanelf call above should probably be addressed in separate follow-up issues." The attached rwx-stack.txt contains libsal_uno.so.3, so it appears that the gentoo-built OOo is also affected by the first problem. Once I successfully have done the verification described in the first problem, it should be clear that this issue is either a duplicate of issue 70840 (in case gentoo uses the same tool chain as Sun to build OOo) or a gentoo-specific issue (in case they use another tool chain which nonetheless has similar shortcommings to those of the Sun tool chain). --------------------------------------------------------------------- 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]
