Page 1 of 1

Viper: taking its own pawn

PostPosted: 10 Aug 2006, 12:32
by Volker Pittlik
In this position

[diag]1q2k1nr/4bppp/B3p3/3pn1P1/N2NP3/4BP2/1PP4P/3Q1RK1 b k - 0 12[/diag]

1q2k1nr/4bppp/B3p3/3pn1P1/N2NP3/4BP2/1PP4P/3Q1RK1 b k - 0 12

Viper as black played e6d5. The game was forfeited.

From the viper.log:

Code: Select all
< ENGINE info multipv 1 depth 9 score cp -481 time 1749 nodes 326745 nps 186818 pv e6d5 e3f4 e7d6 d3a6 g8e7 a6b5 e8f8 a4c3 e5c4 f4d6 b8d6
> XBOARD 9 -481 175 326745
< ENGINE info currmove e8f8 currmovenumber 2
< ENGINE info currmove b8b4 currmovenumber 3
< ENGINE info currmove h7h6 currmovenumber 4
< ENGINE info currmove f7f6 currmovenumber 5
< ENGINE info nodes 380000 nps 186640 time 2036
< ENGINE info currmove b8a7 currmovenumber 6
< ENGINE info currmove b8d6 currmovenumber 7
< ENGINE info currmove e7d6 currmovenumber 8
< ENGINE info currmove e5d7 currmovenumber 9
< ENGINE info currmove b8b7 currmovenumber 10
< ENGINE info currmove e7b4 currmovenumber 11
< ENGINE info currmove e5d3 currmovenumber 12
< ENGINE info currmove a6a5 currmovenumber 13
< ENGINE info currmove h7h5 currmovenumber 14
< ENGINE info currmove e7d8 currmovenumber 15
< ENGINE info currmove b8c7 currmovenumber 16
< ENGINE info currmove e5g6 currmovenumber 17
< ENGINE info currmove g7g6 currmovenumber 18
< ENGINE info currmove b8c8 currmovenumber 19
< ENGINE info currmove b8d8 currmovenumber 20
< ENGINE info currmove e5c4 currmovenumber 21
< ENGINE info currmove e5g4 currmovenumber 22
< ENGINE info currmove g8f6 currmovenumber 23
< ENGINE info currmove e7f8 currmovenumber 24
< ENGINE info currmove e5f3 currmovenumber 25
< ENGINE info currmove e7g5 currmovenumber 26
< ENGINE info currmove b8a8 currmovenumber 27
< ENGINE info currmove e5c6 currmovenumber 28
< ENGINE info currmove e7f6 currmovenumber 29
< ENGINE info currmove e8d7 currmovenumber 30
< ENGINE info currmove e7c5 currmovenumber 31
< ENGINE info currmove e7a3 currmovenumber 32
< ENGINE info currmove f7f5 currmovenumber 33
< ENGINE info currmove e8d8 currmovenumber 34
< ENGINE info currmove g8h6 currmovenumber 35
< ENGINE info nodes 580000 nps 188925 time 3070
< ENGINE info currmove b8b2 currmovenumber 36
< ENGINE info currmove b8b3 currmovenumber 37
< ENGINE info currmove b8b6 currmovenumber 38
< ENGINE info currmove b8b5 currmovenumber 39
< ENGINE bestmove e6d5 ponder e3f4
> XBOARD 9 -481 307 580000
> XBOARD move e6d5
POLYGLOT ILLEGAL MOVE "e6d5"
POLYGLOT 1q2k1nr/4bppp/B3p3/3pn1P1/N2NP3/4BP2/1PP4P/3Q1RK1 b k - 0 12
POLYGLOT
POLYGLOT - q - - k - n r
POLYGLOT - - - - b p p p
POLYGLOT B - - - p - - -
POLYGLOT - - - p n - P -
POLYGLOT N - - N P - - -
POLYGLOT - - - - B P - -
POLYGLOT - P P - - - - P
POLYGLOT - - - Q - R K -
POLYGLOT
POLYGLOT black to play
POLYGLOT
move_step(): illegal move "e6d5"
POLYGLOT *** QUIT ***
> ENGINE quit
< ENGINE EOF


Volker

Re: Viper: taking its own pawn

PostPosted: 10 Aug 2006, 14:09
by Tord Romstad
Hello Volker,

Thanks for the bug report.

Could you please send me the whole viper.log file, or at least a bit more of it? I need everything from the last "position" command sent from PolyGlot until the illegal move occured.

Tord

Re: Viper: taking its own pawn

PostPosted: 10 Aug 2006, 14:21
by Volker Pittlik
Tord Romstad wrote:...
Could you please send me the whole viper.log file, ...


Done

Volker