abrt 1.1.1 detected a crash.
Attached file: backtrace
cmdline: gdb -batch -ex 'set debug-file-directory /usr/lib/debug:/var/cache/abrt-di/usr/lib/debug' -ex 'file /usr/lib/jvm/java-1.6.0-openjdk-126.96.36.199.x86_64/jre/bin/java' -ex 'core-file /var/cache/abrt/ccpp-1277092789-3561/coredump' -ex 'thread apply all backtrace 2048 full' -ex 'info sharedlib' -ex 'print (char*)__abort_msg' -ex 'print (char*)__glib_assert_msg' -ex 'info registers' -ex disassemble
comment: Eclipse crashed (which has been happening a lot). The debug traceback is too big to report though -- abrt doesn't let me. I tried anyway. I opened ABRT to report it, debuginfo packages were downloaded, then got a report that gdb crashed.
reason: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Created attachment 425521 [details]
OS Release: Fedora release 13 (Goddard)
Eclipse crashed (which has been happening a lot). The debug traceback is too big to report though -- abrt doesn't let me. I tried anyway. I opened ABRT to report it, debuginfo packages were downloaded, then got a report that gdb crashed.
#10 0x0000000000512dd5 in val_print_array_elements (
type=<value optimized out>, valaddr=0x11e889e0 "",
address=140161173391296, stream=0x165c9b0, recurse=41342,
That "recurse" value points at the problem.
Without more information I would guess that this is one of:
*** Bug 606472 has been marked as a duplicate of this bug. ***
gdb-7.1-27.fc13 has been submitted as an update for Fedora 13.
gdb-7.1-27.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.