Bug 561107 - SIGSEGV in thread 1 running /usr/bin/elisa (corrupt stack?) with unhandled exception
Summary: SIGSEGV in thread 1 running /usr/bin/elisa (corrupt stack?) with unhandled ex...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: elisa
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Saou
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:027914206f0de7dda4e086de09f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-02 18:07 UTC by Rui Gouveia
Modified: 2010-12-03 23:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 23:25:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (33.15 KB, text/plain)
2010-02-02 18:07 UTC, Rui Gouveia
no flags Details

Description Rui Gouveia 2010-02-02 18:07:03 UTC
abrt 1.0.4 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/elisa
component: python
executable: /usr/bin/python
kernel: 2.6.31.9-174.fc12.i686
package: python-2.6.2-2.fc12
rating: 3
reason: Process was terminated by signal 11
release: Fedora release 12 (Constantine)

Comment 1 Rui Gouveia 2010-02-02 18:07:05 UTC
Created attachment 388359 [details]
File: backtrace

Comment 2 Dave Malcolm 2010-02-11 19:42:23 UTC
Thank you for reporting this bug.

How reproducible is this problem?  If you run the program from a terminal, is an error message printed?

What is the output of running the following command?
  rpm -q elisa

Looking at the backtrace, it looks like thread #2 is somehow running "main", and is in the process of causing the process to exit, due to an unhandled Python exception, but thread #1 has somehow into a bad state that has led to a SIGSEGV.

Unfortunately the stack information of thread #1 doesn't contain any symbolic information which makes this very difficult to analyse further.  It looks to me like the stack of that thread might have been corrupted somehow.

Reassigning component from "python" to "elisa";  hopefully the elisa maintainer will be able to figure this out further or reassign as necessary (knowing what the exception was would be useful, I think, but I suspect this one will be very hard to troubleshoot, alas).

Comment 3 Rui Gouveia 2010-02-25 15:43:20 UTC
Sorry for the delay.

# rpm -q elisa
elisa-0.5.35-2.fc12.noarch

Comment 4 Bug Zapper 2010-11-03 23:14:53 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-03 23:25:58 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.


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