abrt detected a crash. Comment ----- Click "bookmark this page" in firefox. A prompt box for where to store the link appears (I have multiple foldeers). Click to expand the folders. The folder contents begin to appear. Firefox crashes. Attached file: backtrace cmdline: /usr/lib64/firefox-3.5.5/firefox component: firefox executable: /usr/lib64/firefox-3.5.5/firefox kernel: 2.6.31.5-127.fc12.x86_64 package: firefox-3.5.5-1.fc12 rating: 2 reason: Process was terminated by signal 11
Created attachment 369571 [details] File: backtrace
Thank you for taking the time to report this bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash, because there are no debugging symbols loaded (probably abrt failed to load them). Unfortunately, we cannot use this backtrace. Closing as INSUFFICIENT_DATA.
abrt never prompted me to enable the debuginfo repo. Now that I've done so, it is downloading 80 -debuginfo packages. The firefox failure is completely repeatable, so I'll be resubmitting this bug as soon as the downloads finish.
I can reproduce the bug here to.
(In reply to comment #4) > I can reproduce the bug here to. and could you provide better backtrace, please?
What would be the best way to do so ?
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.
(In reply to comment #7) > First of all, could we get output of the command > > rpm -qa *xulrun* *firefox* *mozilla* *flash* *plugin* There it is: $ rpm -qa *xulrun* *firefox* *mozilla* *flash* *plugin* plymouth-plugin-label-0.8.0-0.2009.29.09.19.fc12.x86_64 gstreamer-plugins-flumpegdemux-0.10.15-8.fc12.x86_64 setroubleshoot-plugins-2.1.29-1.fc12.noarch mozilla-filesystem-1.9-5.fc12.x86_64 alsa-plugins-pulseaudio-1.0.21-2.fc12.i686 plymouth-plugin-two-step-0.8.0-0.2009.29.09.19.fc12.x86_64 nspluginwrapper-debuginfo-1.3.0-8.fc12.x86_64 abrt-plugin-logger-0.0.11-2.fc12.x86_64 java-1.6.0-openjdk-plugin-1.6.0.0-33.b16.fc12.x86_64 gstreamer-plugins-base-0.10.25-5.fc12.x86_64 firefox-debuginfo-3.5.5-1.fc12.x86_64 abrt-plugin-sqlite3-0.0.11-2.fc12.x86_64 nspluginwrapper-1.3.0-8.fc12.i686 anaconda-yum-plugins-1.0-5.fc12.noarch totem-mozplugin-2.28.2-2.fc12.x86_64 abrt-plugin-bugzilla-0.0.11-2.fc12.x86_64 PackageKit-yum-plugin-0.5.4-0.1.20091029git.fc12.x86_64 nspluginwrapper-1.3.0-8.fc12.x86_64 firefox-3.5.5-1.fc12.x86_64 gstreamer-plugins-good-0.10.16-7.fc12.x86_64 flash-plugin-10.0.32.18-release.i386 xulrunner-debuginfo-1.9.1.5-1.fc12.x86_64 xulrunner-1.9.1.5-1.fc12.x86_64 alsa-plugins-pulseaudio-1.0.21-2.fc12.x86_64 abrt-plugin-kerneloopsreporter-0.0.11-2.fc12.x86_64 gdm-plugin-fingerprint-2.28.1-24.fc12.x86_64 PackageKit-gstreamer-plugin-0.5.4-0.1.20091029git.fc12.x86_64 > 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 Starting firefox -g starts a gdb console error but not firefox itself. I therefore started firefox myself on another terminal, reproduced the bug. It crashed giving: /usr/lib64/firefox-3.5.5/run-mozilla.sh: line 131: 11280 Segmentation fault (core dumped) "$prog" ${1+"$@"} > (gdb) thread apply all backtrace This doesn't give anything (but I suspect it is related with the fact that firefox -g doesn't start a firefox window) > valgrind --trace-children=yes --log-file=/tmp/firefox-valgrind-log.txt > /usr/bin/firefox Attached to the bug (I had to ctrl+c to stop it)
Created attachment 369878 [details] output from valgrind
Looks like a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=525477 *** This bug has been marked as a duplicate of bug 525477 ***
I have this bug when I copy source code from netbeans and past it in gmain new email.