Bug 673552

Summary: [abrt] gdb-7.2-36.fc14: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: cimed <ion59cimed>
Component: ncursesAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: jan.kratochvil, mlichvar, pmuldoon, sergiodj
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:e7c250da80e3756b397f42edb4201426aa28b0fe
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 14:46:28 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 cimed 2011-01-28 17:12:28 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: gdb -batch -ex 'set debug-file-directory /usr/lib/debug:/var/cache/abrt-di/usr/lib/debug' -ex 'file /bin/bash' -ex 'core-file /var/spool/abrt/ccpp-1296234591-2048/coredump' -ex 'thread apply all backtrace 2048 full' -ex 'info sharedlib' -ex 'print (char*)__abort_msg' -ex 'print (char*)__glib_assert_msg' -ex 'info registers' -ex disassemble
component: gdb
executable: /usr/bin/gdb
kernel: 2.6.35.10-74.fc14.x86_64
package: gdb-7.2-36.fc14
reason: Process /usr/bin/gdb was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1296234725
uid: 500

How to reproduce
-----
1.
2.
3.
Crash gdb

Comment 1 cimed 2011-01-28 17:12:30 UTC
Created attachment 475835 [details]
File: backtrace

Comment 2 Jan Kratochvil 2011-02-01 19:30:55 UTC
Resolved GDB backtrace:
gdb[0x415dc9] = init_page_info + 41
gdb[0x418b05] = initialize_utils + 213
gdb[0x41451a] = gdb_init + 42
gdb[0x40a1b5] = captured_main + 1381
gdb[0x51343b] = catch_errors + 91
gdb[0x40acd4] = gdb_main + 36
gdb[0x4098d9] = main + 105
gdb[0x4097a9] = _start + 41

This is either some broken configuration for ncurses or a random machine crash.

Does memtest86+ pass for you?
Is the problem reproducible?
What is the ncurses package version at the time of this crash?

Anyway unrelated to GDB.

Comment 3 Fedora End Of Life 2012-08-16 14:46:31 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping