Bug 573894 - [abrt] crash in pychess-0.10-0.3.20100214svn.fc12: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in pychess-0.10-0.3.20100214svn.fc12: Process /usr/bin/python wa...
Keywords:
Status: CLOSED DUPLICATE of bug 573893
Alias: None
Product: Fedora
Classification: Fedora
Component: pychess
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Thomas Spura
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:92d5b3c91eff71790b0660206ba...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-16 02:49 UTC by Jesse Larrew
Modified: 2010-03-29 17:57 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-29 17:57:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (213.68 KB, text/plain)
2010-03-16 02:49 UTC, Jesse Larrew
no flags Details

Description Jesse Larrew 2010-03-16 02:49:27 UTC
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/pychess
comment: Threw an exception while trying to save a game in PGN format. Trying to save it again caused the seg fault.
component: pychess
executable: /usr/bin/python
kernel: 2.6.32.9-70.fc12.i686.PAE
package: pychess-0.10-0.3.20100214svn.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 Jesse Larrew 2010-03-16 02:49:33 UTC
Created attachment 400356 [details]
File: backtrace

Comment 2 Thomas Spura 2010-03-16 12:00:27 UTC
Thanks for the bug report.

I guess with "threw an exeption while trying to save a game" you mean the exeption in bug #573893 ?

Comment 3 Jesse Larrew 2010-03-16 15:21:04 UTC
(In reply to comment #2)
> Thanks for the bug report.
> 
> I guess with "threw an exeption while trying to save a game" you mean the
> exeption in bug #573893 ?    

Hi Thomas,

Yup, that's the one! These two occurred together.

Jesse

Comment 4 Thomas Spura 2010-03-19 23:10:13 UTC
Hmm, I don't think this will be reproducable once bug #573893 is gone or what do you think?

Comment 5 Jesse Larrew 2010-03-20 03:08:35 UTC
Most likely not. I think this crash was a result of bug #573893. If you want, feel free to close this bug and simply track 573893. :)

Comment 6 Thomas Spura 2010-03-29 17:57:21 UTC
(In reply to comment #5)
> Most likely not. I think this crash was a result of bug #573893. If you want,
> feel free to close this bug and simply track 573893. :)    

Hmm closing as dublicate should be the best way ;)

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


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