abrt 1.0.9 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/firefox-3.6/firefox component: firefox executable: /usr/lib64/firefox-3.6/firefox global_uuid: 490ef6d982e80cf5057c074fc0b2229c47bb6c91 kernel: 2.6.33.2-57.fc13.x86_64 package: firefox-3.6.3-4.fc13 rating: 4 reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard)
Created attachment 411096 [details] File: backtrace
#2 <signal handler called> No symbol table info available. #3 JS_CallTracer (trc=<value optimized out>, thing=0x7f22b626c870, kind=<value optimized out>) at jsgc.cpp:2615 rt = 0x7f32bd187000 a = <value optimized out> cx = 0x7f32a7c5b800 index = <value optimized out> flagp = 0x7f22b626cf58 <Address 0x7f22b626cf58 out of bounds> #4 0x0000003dba67ff8a in js_TraceObject (trc=0x7fff32660620, obj=0x7f32b6148440) at jsobj.cpp:5706 v = <value optimized out> i = 2 cx = <value optimized out> scope = 0x7f32b61455c0 clasp = <value optimized out> nslots = 7 #5 0x0000003dba65e855 in JS_CallTracer (trc=0x7fff32660620, thing=<value optimized out>, kind=<value optimized out>) at jsgc.cpp:2653 stackDummy = 61 rt = <value optimized out> a = <value optimized out> cx = 0x7f32a7c5b800 index = <value optimized out> flagp = <value optimized out> #6 0x0000003dba625eab in array_trace (trc=0x7fff32660620, obj=0x7f32b59fed80) at jsarray.cpp:1233 capacity = <value optimized out> i = <value optimized out> v = <value optimized out> #7 0x0000003dba65e855 in JS_CallTracer (trc=0x7fff32660620, thing=<value optimized out>, kind=<value optimized out>) at jsgc.cpp:2653 stackDummy = 61 rt = <value optimized out> a = <value optimized out> cx = 0x7f32a7c5b800 index = <value optimized out> flagp = <value optimized out> #8 0x0000003dba67ff8a in js_TraceObject (trc=0x7fff32660620, obj=0x7f32b59fed40) at jsobj.cpp:5706 v = <value optimized out> i = 3 cx = <value optimized out> scope = 0x7f32b59f9e10 clasp = <value optimized out> nslots = 11 #9 0x0000003dba65e855 in JS_CallTracer (trc=0x7fff32660620,
*** This bug has been marked as a duplicate of bug 546861 ***