Re: [Bug-XBoard] xboard crashes with engine

[Eric Mullins]

h.g. muller wrote:
> At 17:56 9-12-2009 -0700, Eric Mullins wrote:
> > Doesn't run an engine properly in xboard.  Engine starts fine, but as 
> > soon as I analyze or make a move, it crashes.  Don't know why the 
> > output log is winboard.debug... really it is xboard.
>
> The wrong default name of the debug file was introduced when porting 
> the WB option-handling code to XBoard, and should have been fixed by now.
>
> From the log files you gave, it seems this is an issue between Toga 
> and Polyglot:
> At the end Polyglot complains it receives an EOF from the engine.
> This is not something that XBoard can have any say in.

I added the book to the command so that the engine would respond w/out 
thinking.  winboard.debug terminates with:

6436 >first : time 30000
6436 >first : otim 30000
book hit = (NULL)
6436 >first : usermove 6436 >first : g1f3
6462 <first : 1 +1 0 0 Nf6

and polyglot.log terminates with:
1261610611.813 Adapter->Engine: go wtime 300000 btime 300000 movestogo 40
1261610611.838 Engine->Adapter: info multipv 1 depth 1 seldepth 0 score 
cp 1 time 0 nodes 0 pv g8f6
1261610611.838 Adapter->GUI: 1 +1 0 0 Nf6
1261610611.838 Engine->Adapter: info time 0 nodes 0 nps 0 cpuload 0
1261610611.838 Engine->Adapter: info hashfull 0
1261610611.839 Engine->Adapter: bestmove g8f6
1261610611.839 Adapter->GUI: 1 +1 0 0 Nf6
1261610611.839 Adapter->GUI: tellics kibitzalias depth=1 time=0.00 
node=0 speed=0 score=+0.01 pv="Nf6"
1261610611.839 Adapter->GUI: move g8f6
1261610611.839 POLYGLOT MOVE Nf6
1261610611.839 POLYGLOT THINK -> WAIT
1261610611.847 GUI->Adapter: EOF
1261610611.847 POLYGLOT *** QUIT ***
1261610611.847 Adapter->Engine: quit
1261610611.847 POLYGLOT Closing engine
1261610611.847 Adapter->Engine: EOF
1261610611.958 Engine->Adapter: EOF
1261610611.958 POLYGLOT Calling exit

Seems to me that xboard crashed and that's how the first GUI->Adapter: 
EOF occurs.
> You are not using bitbases in Toga, by any chance?

No.  Should be evident from the logs that egbb wasn't used.

I don't think this is an engine or adapter problem.  The Xboard crash 
looks like some Xt issue to me.


The same script works fine if I substitute xboard (master-20091122) with 
4.4.0.beta1 or 4.2.7.