Bug 541691 - Emacs MI crash
Summary: Emacs MI crash
Keywords:
Status: CLOSED DUPLICATE of bug 682286
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2baacded558ffa16500fdde5afd...
: 557923 559747 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-26 18:25 UTC by Mark Lees
Modified: 2011-03-11 19:11 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-11 19:11:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (5.55 KB, text/plain)
2009-11-26 18:25 UTC, Mark Lees
no flags Details

Description Mark Lees 2009-11-26 18:25:31 UTC
abrt detected a crash.

Attached file: backtrace
cmdline: gdb --interpreter mi2 --nx
component: gdb
executable: /usr/bin/gdb
kernel: 2.6.31.5-127.fc12.x86_64
package: gdb-7.0-3.fc12
rating: 3
reason: Process was terminated by signal 11

Comment 1 Mark Lees 2009-11-26 18:25:34 UTC
Created attachment 374048 [details]
File: backtrace

Comment 2 Karel Klíč 2010-02-24 17:00:18 UTC
*** Bug 557923 has been marked as a duplicate of this bug. ***

Comment 3 Karel Klíč 2010-02-24 17:00:23 UTC
*** Bug 559747 has been marked as a duplicate of this bug. ***

Comment 4 Bug Zapper 2010-11-04 05:14:21 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 5 Bug Zapper 2010-12-04 02:44:18 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 Bug Zapper 2010-12-05 06:21:04 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 7 Jan Kratochvil 2010-12-06 00:10:22 UTC
Last verification has been done on f12.

Comment 8 Fedora Admin XMLRPC Client 2011-01-06 03:23:54 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 9 Jan Kratochvil 2011-03-11 19:11:29 UTC

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


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