Red Hat Bugzilla – Bug 589765
[abrt] crash in gdb-7.0.1-45.fc12: raise: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
Last modified: 2010-05-25 05:32:26 EDT
abrt 1.0.9 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/bin/wesnoth' -ex 'core-file /var/cache/abrt/ccpp-1273176518-4877/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: I don't know what exactly caused this. My desktop got jacked up after the crash to desktop from BoW. I had it set at 1248x768 and now the pixels are stretched to make the screen look like 800x600 (desktop icons are dropping below the GNOME desktop tool bar on the bottom and my mouse can exceed it).
reason: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
How to reproduce
1. Battle for Wesnoth crashes to desktop after 7 or 8 units have 3 moves pre-queued. Stack trace for that crash stated (at the end): virtual memory exhausted: can't allocate 1700946284 bytes.
2. While abrt was generating the report for the above bug, I got a bunch of abrt error windows open saying that the report size quota was exceeded; this bug was among the options.
Created attachment 412157 [details]
*** This bug has been marked as a duplicate of bug 568248 ***
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #568248.
Sorry for the inconvenience.