Bug 571510 - [abrt] crash in gdb-7.0.1-33.fc12: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gdb-7.0.1-33.fc12: Process /usr/bin/gdb was killed by signal ...
Keywords:
Status: CLOSED DUPLICATE of bug 627456
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c0d7c28f5bc95780455d49a885a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-08 17:33 UTC by Alex Chernyakhovsky
Modified: 2010-08-26 08:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-03 21:31:20 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (9.23 KB, text/plain)
2010-03-08 17:33 UTC, Alex Chernyakhovsky 		no flags Details
View All

Description Alex Chernyakhovsky 2010-03-08 17:33:47 UTC 
abrt 1.0.7 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/gdb --annotate=3 sim
comment: This has only happened once so far, not entirely sure why.
component: gdb
executable: /usr/bin/gdb
kernel: 2.6.32.9-67.fc12.x86_64
package: gdb-7.0.1-33.fc12
rating: 4
reason: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Use GDB within emacs, stepping through code
2. Restart programming being debugged (with 'r')
3. Observe GDB crash
Comment 1 Alex Chernyakhovsky 2010-03-08 17:33:49 UTC 
Created attachment 398571 [details]
File: backtrace
Comment 2 Jan Kratochvil 2010-04-03 21:31:20 UTC 
Crash is on accessing `value->enclosing_type->main_type->'.
Guessing it is due to changed binary which is still loaded in GDB.
GDB does reread_symbols in such case which is a bit broken function.
The problem is known and fix is planned, there was already one attempt:
http://sourceware.org/ml/gdb-patches/2009-06/msg00679.html
Comment 3 Jan Kratochvil 2010-08-26 08:25:00 UTC 

*** This bug has been marked as a duplicate of bug 627456 ***
Note You need to log in before you can comment on or make changes to this bug.