Bug 607043

Summary: [abrt] crash in gdb-7.1-26.fc13: raise: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Ty Talmadge <drown_rat>
Component: gdbAssignee: Jan Kratochvil <jan.kratochvil>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: jan.kratochvil, pmuldoon, swagiaal
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:b6346f02c1de6d8393e486d6714337110946e518
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-27 17:43:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Ty Talmadge 2010-06-23 02:45:22 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/gdb -nw -n -batch -x /tmp/kde-ty/drkonqiyp3902.tmp -p 3839 /usr/bin/amarok
component: gdb
crash_function: raise
executable: /usr/bin/gdb
global_uuid: b6346f02c1de6d8393e486d6714337110946e518
kernel: 2.6.33.5-112.fc13.i686.PAE
package: gdb-7.1-26.fc13
rating: 4
reason: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. installing amarok using the wrong libraries
2.
3.
Comment 1 Ty Talmadge 2010-06-23 02:45:24 UTC 
Created attachment 426138 [details]
File: backtrace
Comment 2 Jan Kratochvil 2010-06-27 17:43:43 UTC 
There is handle_sigterm which means GDB caught SIGTERM, it must have been killed by an external process.  While it should not crash even in such case I am not going to resolve such problem, GDB is currently not suitable to handle it.