abrt 1.0.4 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/firefox-3.5.6/firefox comment: I don't think it's possible to reproduce it. component: firefox executable: /usr/lib64/firefox-3.5.6/firefox kernel: 2.6.31.12-174.2.3.fc12.x86_64 package: firefox-3.5.6-1.fc12 rating: 3 reason: Process was terminated by signal 11 (Segmentation fault) release: Fedora release 12 (Constantine) How to reproduce: 1. I just ran firefox. Maybe there was a thread hanged in the background of which I was not aware of.
Created attachment 389383 [details] File: backtrace
#2 <signal handler called> No symbol table info available. #3 0x000000318d423b65 in g_type_check_instance () from /lib64/libgobject-2.0.so.0 No symbol table info available. #4 0x000000318d422eab in g_signal_handlers_disconnect_matched () from /lib64/libgobject-2.0.so.0 No symbol table info available. #5 0x00007f5d245fcec3 in g_utf8_prev_char () from /usr/lib64/gtk-2.0/2.10.0/immodules/im-xim.so No symbol table info available. #6 0x00007f5d245fcf5b in g_utf8_prev_char () from /usr/lib64/gtk-2.0/2.10.0/immodules/im-xim.so No symbol table info available. #7 0x000000318d40ba8e in g_closure_invoke () from /lib64/libgobject-2.0.so.0 No symbol table info available. #8 0x000000318d420ec3 in ?? () from /lib64/libgobject-2.0.so.0 No symbol table info available. #9 0x000000318d422259 in g_signal_emit_valist () from /lib64/libgobject-2.0.so.0 No symbol table info available. #10 0x000000318d4227a3 in g_signal_emit () from /lib64/libgobject-2.0.so.0 No symbol table info available. #11 0x000000318e8200d2 in gdk_display_close () from /usr/lib64/libgdk-x11-2.0.so.0 No symbol table info available. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Thank you for taking the time to submit this bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** This bug has been marked as a duplicate of bug 543165 ***