Bug 593268 - [abrt] crash in gdb-7.0.1-45.fc12: raise: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
[abrt] crash in gdb-7.0.1-45.fc12: raise: Process /usr/bin/gdb was killed by ...
Status: CLOSED DUPLICATE of bug 545092
Product: Fedora
Classification: Fedora
Component: gdb (Show other bugs)
12
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Jan Kratochvil
Fedora Extras Quality Assurance
abrt_hash:b6a45f2ec07553e056d8b7b85fe...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-18 07:55 EDT by Damian Wrobel
Modified: 2010-05-25 05:58 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 05:58:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (10.30 KB, text/plain)
2010-05-18 07:55 EDT, Damian Wrobel
no flags Details

  None (edit)
Description Damian Wrobel 2010-05-18 07:55:30 EDT
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gdb -q -fullname ./ocap10dvrhn_probe_sny_intel_cp_internal_intelce3100_hwdbg_fl
comment: just debugging an application
component: gdb
crash_function: raise
executable: /usr/bin/gdb
global_uuid: b6a45f2ec07553e056d8b7b85fe753a29ced720f
kernel: 2.6.32.11-99.fc12.i686.PAE
package: gdb-7.0.1-45.fc12
rating: 4
reason: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 Damian Wrobel 2010-05-18 07:55:32 EDT
Created attachment 414819 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 05:58:23 EDT

*** This bug has been marked as a duplicate of bug 545092 ***
Comment 3 Karel Klíč 2010-05-25 05:58:23 EDT
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #545092.

Sorry for the inconvenience.

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