"emerge virtualbox" generated the following warnings: QA Notice: the following files contain runtime text relocations Text relocations force the dynamic linker to perform extra work at startup, waste system resources, and may pose a security risk. On some architectures, the code may not even function properly, if at all. For more information, see http://hardened.gentoo.org/pic-fix-guide.xml Please include this file in your report: /var/tmp/portage/virtualbox-9999/temp/scanelf-textrel.log TEXTREL opt/VirtualBox/VBoxC.so TEXTREL opt/VirtualBox/VBoxDD.so TEXTREL opt/VirtualBox/VBoxDD2.so TEXTREL opt/VirtualBox/VBoxREM.so TEXTREL opt/VirtualBox/VBoxRT.so TEXTREL opt/VirtualBox/VBoxVMM.so TEXTREL opt/VirtualBox/VBoxXML.so TEXTREL opt/VirtualBox/components/VBoxC.so QA Notice: the following files contain executable stacks Files with executable stacks will not work properly (or at all!) on some architectures/operating systems. A bug should be filed at http://bugs.gentoo.org/ to make sure the file is fixed. For more information, see http://hardened.gentoo.org/gnu-stack.xml Please include this file in your report: /var/tmp/portage/virtualbox-9999/temp/scanelf-execstack.log RWX --- --- opt/VirtualBox/VBoxVMM.so A Segmentation fault occurred after executing virtualbox. Reproducible: Always Steps to Reproduce: 1. emerge virtualbox 2. virtualbox 3. Actual Results: Actual results are listed in the Description Expected Results: The system seg faulted after executing virtualbox The files /var/tmp/portage/virtualbox-9999/temp/scanelf-textrel.log and /var/tmp/portage/virtualbox-9999/temp/scanelf-execstack.log were non-existent.
Just a WAG, but for me the problem was PAX (vbox does some nasty stuff with marking memory as executable), and using paxctl to disable all security features on the vbox executable (VBoxVRDP in my case) fixed the crashes. I still have to do some detailed testing which bit exactly solved the problem.
Well I'd say we tag it upstream then as this isn't gentoo specific ;)
*** Bug 212972 has been marked as a duplicate of this bug. ***
(In reply to comment #2) > Well I'd say we tag it upstream then as this isn't gentoo specific ;) > yes, i can confirm that this issue was reported time ago to upstream
