Libre Office double mmaps a temporary file to build trampolines block. It attempts to create the temporary file in $HOME, and fallbacks on /tmp:
236 #ifdef USE_DOUBLE_MMAP
237 bool VtableFactory::createBlock(Block &block, sal_Int32 slotCount) const
But $HOME is more likely to be noexec, so it is better to try /tmp first. Using $HOME first can also create annoying complains in LSM such as SELinux or AppArmor.
As an example, libffi tries the following directories, in this order, until it finds something suitable:
6. whatever is listed in /etc/mtab,
7. whatever is listed in /proc/mounts
T'was Caolan who first told me of the existence of this magic =)
I just used /home falling back to /tmp because Ulrich indicated that the temp dirs were more likely to have noexec set (http://www.akkadia.org/drepper/selinux-mem.html)
Should be fairly easy to adapt the code to look in more places and reorder the places it checks, I've no problem with applying any patch that does that. Not on my own current radar to do it though, so I'll set the easyhack flags
Migrating Whiteboard tags to Keywords: (easyHack, difficultyBeginner, skillCpp)
note that the likelihood of actually executing the double-mmap code paths severely decreased with <http://cgit.freedesktop.org/libreoffice/core/commit/?id=8b9968a26265facaf5e761485d750ce9cedab3ab> "fdo#72755: Only use double mmap as fallback"
No code pointer
JanI is default CC for Easy Hacks (Add Jan; remove LibreOffice Dev List from CC)
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker