Bug 676440

Summary: [abrt] gdb-7.2-36.fc14: __libc_message: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: P. Ignacio Q. <dreamer86>
Component: gdbAssignee: Jan Kratochvil <jan.kratochvil>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: jan.kratochvil, pmuldoon, sergiodj
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:00eeeb7f7c804b79537323514605d1fc4a22c941
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-24 02:05:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description P. Ignacio Q. 2011-02-09 21:06:02 UTC 
abrt version: 1.1.14
architecture: i686
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/conky' -ex 'core-file /var/spool/abrt/ccpp-1297285343-2887/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
component: gdb
crash_function: __libc_message
executable: /usr/bin/gdb
kernel: 2.6.35.10-74.fc14.i686.PAE
package: gdb-7.2-36.fc14
rating: 4
reason: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1297285402
uid: 1000

How to reproduce
-----
1.Trying to repport a bug.
2.
3.
Comment 1 P. Ignacio Q. 2011-02-09 21:06:04 UTC 
Created attachment 477908 [details]
File: backtrace
Comment 2 Jan Kratochvil 2011-02-24 02:05:15 UTC 
I believe it is unreproducible, cannot debug.
If you have it reproducible with the core file /var/spool/abrt/ccpp-1297285343-2887/coredump please reopen the bug.