Bug 607043 - [abrt] crash in gdb-7.1-26.fc13: raise: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gdb-7.1-26.fc13: raise: Process /usr/bin/gdb was killed by si...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b6346f02c1de6d8393e486d6714...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-23 02:45 UTC by Ty Talmadge
Modified: 2010-06-27 17:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-27 17:43:43 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (19.63 KB, text/plain)
2010-06-23 02:45 UTC, Ty Talmadge 		no flags Details
View All

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