abrt 1.0.8 detected a crash. architecture: i686 cmdline: /usr/bin/python /usr/bin/pychess comment: Tried to undo a move in a game using the gnuchess engine. component: pychess executable: /usr/bin/pychess kernel: 2.6.32.9-70.fc12.i686.PAE package: pychess-0.10-0.3.20100214svn.fc12 reason: CECPEngine.py:649:__parseLine:PlayerIsDead: Board didn't validate after move release: Fedora release 12 (Constantine) backtrace ----- CECPEngine.py:649:__parseLine:PlayerIsDead: Board didn't validate after move Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/pychess/Players/CECPEngine.py", line 607, in parseLines self.__parseLine(line) File "/usr/lib/python2.6/site-packages/pychess/Players/CECPEngine.py", line 649, in __parseLine raise PlayerIsDead, "Board didn't validate after move" PlayerIsDead: Board didn't validate after move Local variables in innermost frame: self: GNU Chess 5.07 line: '8. ... c8e6\n' move: c8e6 parts: ['8.', '...', 'c8e6'] movestr: 'c8e6' How to reproduce ----- 1. Install Gnu Chess. 2. Start a new game: Human vs. Gnu Chess. 3. Play a few moves. 4. Undo the last move.
Created attachment 400547 [details] File: backtrace
Thanks for the bug report. I just tried to reproduce this, but without luck... (But I'm running F-13) Did that happen only once, or can you still reproduce this? Maybe you could note, which moves you did. Could you post the output of "rpm -qa gnuchess"?
I'm using gnuchess-5.07-14.fc12.i686. I was able to get it to break again, but I had to undo/redo moves several times to break it (although it didn't trigger ABRT this time). Looking at the logs for gnuchess, it appears that gnuchess is trying to play impossible moves. I think pychess is right to declare the engine dead after this. This may actually be a bug in gnuchess. I'll post the logs to this bz.
Created attachment 401385 [details] gnuchess output. gnuchess output.
Created attachment 401386 [details] pychess output. pychess stdout.
(In reply to comment #3) > I'm using gnuchess-5.07-14.fc12.i686. > Looking at the logs > for gnuchess, it appears that gnuchess is trying to play impossible moves. I > think pychess is right to declare the engine dead after this. This may actually > be a bug in gnuchess. I'll post the logs to this bz. -> Assigning to gnuchess
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
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.