Bug 674118

Summary: [abrt] gdb-7.2-36.fc14: check_typedef: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Erwan Legrand <redhat>
Component: gdbAssignee: Jan Kratochvil <jan.kratochvil>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: jan.kratochvil, pmuldoon, sergiodj, tromey
Target Milestone: ---Flags: tromey: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:ba3f08cbdea583f81c34b612c36e99057270b70c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-01 19:49:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Erwan Legrand 2011-01-31 17:35:20 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: gdb --interpreter mi2 --nx
component: gdb
crash_function: check_typedef
executable: /usr/bin/gdb
kernel: 2.6.35.10-74.fc14.x86_64
package: gdb-7.2-36.fc14
rating: 4
reason: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1296495171
uid: 500

How to reproduce
-----
1. Step through a running process from within Eclipse CDT
2.
3.
Comment 1 Erwan Legrand 2011-01-31 17:35:24 UTC 
Created attachment 476237 [details]
File: backtrace
Comment 2 Tom Tromey 2011-02-01 19:49:41 UTC 

*** This bug has been marked as a duplicate of bug 671533 ***