Bug 625127 - [abrt] crash in gdb-7.0.1-49.fc12: gdbarch_data: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gdb-7.0.1-49.fc12: gdbarch_data: Process /usr/bin/gdb was kil...
Status: CLOSED DUPLICATE of bug 610986
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb (Show other bugs)
(Show other bugs)
Version: 12
Hardware: x86_64 Linux
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:b12f591a3e75dffe9cac1475b67...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-18 16:30 UTC by Patryk Obara
Modified: 2013-03-13 04:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-18 16:43:23 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (14.70 KB, text/plain)
2010-08-18 16:30 UTC, Patryk Obara
no flags Details

Description Patryk Obara 2010-08-18 16:30:55 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/gdb --cd=. --interpreter=mi2 /home/dreamer_/src/evenes-extensions/work/run/lib/opera/opera
component: gdb
crash_function: gdbarch_data
executable: /usr/bin/gdb
global_uuid: b12f591a3e75dffe9cac1475b67362f132b4f697
package: gdb-7.0.1-49.fc12
rating: 4
reason: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
How to reproduce:
1. I don't know; random crash while debugging (I used gdb through nemiver)

Comment 1 Patryk Obara 2010-08-18 16:30:57 UTC
Created an attachment (id=439438)
File: backtrace

Comment 2 Jan Kratochvil 2010-08-18 16:43:23 UTC

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

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