Bug 676440 - [abrt] gdb-7.2-36.fc14: __libc_message: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
Summary: [abrt] gdb-7.2-36.fc14: __libc_message: Process /usr/bin/gdb was killed by si...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:00eeeb7f7c804b7953732351460...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-09 21:06 UTC by P. Ignacio Q.
Modified: 2011-02-24 02:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-24 02:05:15 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (7.24 KB, text/plain)
2011-02-09 21:06 UTC, P. Ignacio Q. 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.