Tyler2004 / pychess

Automatically exported from code.google.com/p/pychess
GNU General Public License v3.0
1 stars 0 forks source link

PyChess doesn't display any tellusererror messages when engine quits #611

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
An engine might encounter a fatal error, fire off a descriptive "tellusererror" 
and terminate. But as soon as the engine quits, PyChess will just display the 
big "Engine, X, has died" dialog instead of leaving any tellusererror messages 
that immediately preceded the engine's termination on screen. Therefore, 
detailed crash or error information provided by the engine won't be visible to 
the user.

What steps will reproduce the problem?
1. Write up an engine that emits tellusererror and then immediately terminates 
under some condition
2. Use the engine in PyChess and trigger above condition

What is the expected output? What do you see instead?
Expected: I can see the "tellusererror" with possible crash or termination 
details. Actual output: I just see the usual default "Engine, X, has died" 
dialog

Does it happen every time?
yup

What version of the product are you using?
PyChess Staunton 0.10beta3

Did you use an installed version of PyChess or did you run in from a
tarball/svn?
Fedora 13's packaged version

Original issue reported on code.google.com by jonas.thiem@gmail.com on 1 Nov 2010 at 5:26

GoogleCodeExporter commented 9 years ago

Original comment by gbtami on 4 Dec 2010 at 10:19

GoogleCodeExporter commented 9 years ago
Since I was recently checking out UCI, it is even more of a problem there (by 
protocol design) since there doesn't appear to be a way for the engine to 
report an error - odd. That's quite an oversight IMHO...

Original comment by jonas.thiem@gmail.com on 30 Aug 2012 at 7:11

GoogleCodeExporter commented 9 years ago

Original comment by gbtami on 20 Apr 2013 at 8:11