Created attachment 422762 [details] Screen shot of firefox segmentation violation Description of problem: Firefox segmentation violation Version-Release number of selected component (if applicable): firefox-3.6.3-4 How reproducible: 100% Steps to Reproduce: Configure Fedora as MLS/Enforcing Start Firefox http://www.nall.com/blog/?p=7 Actual results: Firefox dies Expected results: Firefox starts. Additional info: I expect this is a bad policy interaction - but firefox should not segfault.
Do you have the allow_execmem boolean turned on?
That was it. Thanks Dan.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. First of all, could we get output of the command rpm -qa \*xulrun\* \*firefox\* \*mozilla\* \*flash\* \*plugin\* Please also install firefox-debuginfo (debuginfo-install is from yum-utils package). debuginfo-install firefox Then run firefox with a parameter -g. That will start firefox running inside of gdb debugger. Then use command run and do whatever you did to make firefox crash. When it happens, you should go back to the gdb and run (gdb) thread apply all backtrace This produces usually many screens of the text. Copy all of them into a text editor and attach the file to the bug as an uncompressed attachment. Please, install also valgrind (from valgrind package) and run valgrind --trace-children=yes --log-file=/tmp/firefox-valgrind-log.txt /usr/bin/firefox (that's one line command, browser breaking this line into two notwithstanding) Please, attach the file /tmp/firefox-valgrind-log.txt to this bug as an attachment as well. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Reporter, I interpret Comment 2 to mean that this is not a bug. If this is true, please set this report closed NOTABUG. If there is still an issue, and this is a reproducible crash, please give us the steps to reproduce it for troubleshooting, thank you. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers