Version-Release number of selected component: seamonkey-2.23-1.fc19 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/lib64/seamonkey/seamonkey crash_function: readByte executable: /usr/lib64/seamonkey/seamonkey kernel: 3.12.5-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 readByte at /usr/src/debug/seamonkey-2.23/comm-release/mozilla/js/src/jit/CompactBuffer.h:57 #1 readVariableLength at /usr/src/debug/seamonkey-2.23/comm-release/mozilla/js/src/jit/CompactBuffer.h:40 #2 readUnsigned at /usr/src/debug/seamonkey-2.23/comm-release/mozilla/js/src/jit/CompactBuffer.h:72 #3 read at /usr/src/debug/seamonkey-2.23/comm-release/mozilla/js/src/jit/x64/Assembler-x64.cpp:220 #4 js::jit::Assembler::TraceJumpRelocations at /usr/src/debug/seamonkey-2.23/comm-release/mozilla/js/src/jit/x64/Assembler-x64.cpp:252 #5 js::jit::IonCode::trace at /usr/src/debug/seamonkey-2.23/comm-release/mozilla/js/src/jit/Ion.cpp:665 #6 MarkChildren at /usr/src/debug/seamonkey-2.23/comm-release/mozilla/js/src/gc/Marking.cpp:1185 #7 js::GCMarker::processMarkStackOther at /usr/src/debug/seamonkey-2.23/comm-release/mozilla/js/src/gc/Marking.cpp:1356 #8 processMarkStackTop at /usr/src/debug/seamonkey-2.23/comm-release/mozilla/js/src/gc/Marking.cpp:1423 #9 js::GCMarker::drainMarkStack at /usr/src/debug/seamonkey-2.23/comm-release/mozilla/js/src/gc/Marking.cpp:1524
Created attachment 842719 [details] File: backtrace
Created attachment 842720 [details] File: cgroup
Created attachment 842721 [details] File: core_backtrace
Created attachment 842722 [details] File: dso_list
Created attachment 842723 [details] File: environ
Created attachment 842724 [details] File: exploitable
Created attachment 842725 [details] File: limits
Created attachment 842726 [details] File: maps
Created attachment 842727 [details] File: open_fds
Created attachment 842728 [details] File: proc_pid_status
Created attachment 842729 [details] File: var_log_messages
This is an automated bug update. If you can reproduce the bug, please reopen and remove the [abrt] string from subject. Thanks!