Fedora Account System
Red Hat Associate
Red Hat Customer
abrt 1.0.0 detected a crash. Attached file: backtrace cmdline: /usr/lib/firefox-3.5.5/firefox component: firefox executable: /usr/lib/firefox-3.5.5/firefox kernel: 2.6.31.5-127.fc12.i686 package: firefox-3.5.5-1.fc12 rating: 3 reason: Process was terminated by signal 11
Created attachment 375506 [details] File: backtrace
Thread 1 (Thread 31381): #0 0x00611416 in __kernel_vsyscall () No symbol table info available. #1 0x006f2000 in raise (sig=11) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:42 resultvar = <value optimized out> resultvar = <value optimized out> pid = <value optimized out> #2 0x03580547 in nsProfileLock::FatalSignalHandler ( signo=<value optimized out>) at nsProfileLock.cpp:212 unblock_sigs = {__val = {1024, 0 <repeats 31 times>}} oldact = <value optimized out> #3 <signal handler called> No symbol table info available. #4 0x003fdc7e in g_type_check_instance () from /lib/libgobject-2.0.so.0 No symbol table info available. #5 0x003fcfa6 in g_signal_handlers_disconnect_matched () from /lib/libgobject-2.0.so.0 No symbol table info available. #6 0x02bcf5de in update_client_widget (context_xim=<value optimized out>) at gtkimcontextxim.c:1641 new_client_widget = 0x0 #7 set_ic_client_window (context_xim=<value optimized out>) at gtkimcontextxim.c:654 No locals. #8 0x02bcf681 in xim_info_display_closed (display=<value optimized out>, is_error=<value optimized out>, info=<value optimized out>) at gtkimcontextxim.c:402 ics = 0xa8ffb978 tmp_list = <value optimized out> #9 0x003f3218 in g_cclosure_marshal_VOID__BOOLEAN () from /lib/libgobject-2.0.so.0 No symbol table info available. #10 0x003e55b3 in g_closure_invoke () from /lib/libgobject-2.0.so.0 No symbol table info available. #11 0x003fb118 in ?? () from /lib/libgobject-2.0.so.0 No symbol table info available. #12 0x003fc47d in g_signal_emit_valist () from /lib/libgobject-2.0.so.0 No symbol table info available. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** This bug has been marked as a duplicate of bug 543513 ***