Bug 596251 - [abrt] crash in gdb-7.1-22.fc13: raise: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gdb-7.1-22.fc13: raise: Process /usr/bin/gdb was killed by si...
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:16f5c9dc019d567d61f376154b8...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-26 13:12 UTC by Tomáš Trnka
Modified: 2010-06-02 14:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-06-02 14:27:01 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (15.19 KB, text/plain)
2010-05-26 13:12 UTC, Tomáš Trnka
no flags Details

System ID Private Priority Status Summary Last Updated
Sourceware 11657 0 None None None Never

Description Tomáš Trnka 2010-05-26 13:12:06 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gdb klipper
comment: This happens every time I try to debug klipper from kdebase-workspace-4.4.3-1.fc13.1.x86_64
component: gdb
crash_function: raise
executable: /usr/bin/gdb
global_uuid: 16f5c9dc019d567d61f376154b823360bd695ac0
package: gdb-7.1-22.fc13
rating: 4
reason: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1.gdb klipper
2.break KPixmapCache::find, yes, make it pending
3.run --nocrashhandler --nofork

Comment 1 Tomáš Trnka 2010-05-26 13:12:08 UTC
Created attachment 416822 [details]
File: backtrace

Comment 2 Tomáš Trnka 2010-05-26 13:24:14 UTC
Oops, sorry, the break in question is KIconCache::find, not KPixmapCache::find (that one works okay)...

Note You need to log in before you can comment on or make changes to this bug.