Bright 0.4a, Winboard and ICC...

[swami]

Since H.G.Muller asked me to post the debug file and let the author (Allard) know about what really was wrong with the commands. I decided to post the debug text from winboard-debug here.

I was planning to use ChessPartner GUI but then I liked the winboard enough to want to switch it over to. Winboard x has been giving me errors whereas ChessPartner didn't. That led me to believe there was either a bug in winboard or an engine itself. Once this bug has been erased, then I can look forward using winboard CCT 11 version in the upcoming CCT tournament.

So, Can anyone look into it and tell me what specific command is buggy in Bright?

Thanks for any help.

parseboard 119, castling = -1 -1 6 -1 -1 -1
accepted move Kg1 from ICS, parse it.
moveNum = 119
board = 0-8 x 8
move to parse: Kg1
Parser Qa1: yyleng=3, 21(-1,-1)-(6,0) = 0 ( )
Disambiguate in: 21(-1,-1)-(6,0) = 0 (-)
Disambiguate out: 21(5,0)-(6,0) = 0 (-)
CoordsToAlgebraic, piece=21 (5,0)-(6,0) -
Move parsed to 'Kg1 (0:02)'
time odds: 1 1
Interrupting first
166000 >first : time 400
166000 >first : otim 700
166000 >first : usermove 166000 >first : f1g1
nps: w=-1, b=-1
Display title 'Tinker (8) vs. Swaminathan (9) {1 0}, gameInfo.variant = 0'
<ICS: aics%
ics input 119, castling = -1 -1 6 -1 -1 -1
166016 <first : 1 281 0 1 c6b7
166016 <first : 1 289 0 4 c6d7
166016 <first : 1 301 0 7 c6d5
166016 <first : 2 298 0 52 c6d5 f4f5
166016 <first : 2 303 0 89 g7g6 h3h4
166016 <first : 3 299 0 737 g7g6 h3h4 c6d5
166016 <first : 4 314 0 1046 g7g6 h3h4 c6d5 g1f1
166016 <first : 5 302 0 1312 g7g6 h3h4 c6b7 g1f1 b7d5
166016 <first : 6 311 0 1938 g7g6 h3h4 c6b7 g1f1 b7d5 f1g1
166016 <first : 7 291 0 3086 g7g6 h3h4 c6d5 g1f1 d5b7 f1g1 b7c6
166016 <first : 8 306 16 13549 g7g6 h3h4 c6d5 g1f1 d5b7 f1e1 b7c6 e1f1
166016 <first : 9 288 16 25954 g7g6 h3h4 c6d5 g1f1 d5b7 f1e1 b7a8 f4f8 a8d5
166032 <first : 10 307 32 52763 g7g6 h3h4 c6d5 g1f1 d5b7 f1e1 b7a8 e1d1 a8c6 d1e1
166079 <first : 11 291 78 112641 g7g6 h3h4 c6d5 g1f1 d5b7 f1e1 b7a8 e1d1 a8d5 d1c1 b2e2
166219 <first : 12 289 219 346983 g7g6 h3h4 c6d5 g1f1 d5b7 f1e1 b7a8 e1d1 a8c6 d1e1 b2h2 e1f1
166547 <first : 13 285 547 898098 g7g6 h3h4 c6d5 g1f1 d5b7 f1e1 b7a8 e1d1 a8c6 d1c1 b2h2 c1d1 c6d5
167188 <first : 14 280 1188 2042079 g7g6 h3h4 c6d5 g1f1 d5b7 f1e1 b7a8 e1d1 a8c6 d1c1 b2h2 c1d1 h2g2 f4f8
167563 <first : move g7g6
machine move 119, castling = -1 -1 6 -1 -1 -1
move to parse: g7g6
-1 -1 6 -1 -1 7 Legality test? g7g6
>ICS: g7g6\012
>ICS: kibitz 14/+2.80 (11.88 sec, 2042079 nodes, 172 knps) PV = g7g6 h3h4 c6d5 g1f1 d5b7 f1e1 b7a8 e1d1 a8c6 d1c1 b2h2 c1d1 h2g2 f4f8\012
CoordsToAlgebraic, piece=43 (6,6)-(6,5) -
move: g7g6
, parse: Kg6 (
)
167563 <first : 1 279 0 1 h3h4 c6b7
167563 <first : 1 299 0 6 h3h4 c6d5
167563 <first : 2 314 0 45 h3h4 c6d5 g1f1
167563 <first : 3 282 0 105 h3h4 c6d5 g1f1 d5b7
167563 <first : 4 291 0 263 h3h4 c6d5 g1f1 d5b7 f1g1
167563 <first : 5 291 0 489 h3h4 c6d5 g1f1 d5b7 f1g1 b7c6
167563 <first : 6 306 0 852 h3h4 c6d5 g1f1 d5b7 f1e1 b7c6 e1f1
167563 <first : 7 288 0 1272 h3h4 c6d5 g1f1 d5b7 f1e1 b7a8 f4f8 a8d5
167563 <first : 8 311 0 3699 h3h4 c6d5 g1f1 d5b7 f1e1 b7a8 e1f1 a8d5 f1g1
167579 <first : 9 271 0 10050 h3h4 c6d5 g1f1 d5b7 f1e1 b7a8 e1d1 b2f2 d1c1 a8b7
167610 <first : 10 269 47 84345 h3h4 c6d5 g1f1 d5b7 f1e1 b7a8 e1d1 b2f2 d1c1 f2f3 f4d4 f3f1 c1c2
167625 <first : 10 277 62 111691 h3h4 b2c2 f4f8 c6d5 f3f4 c2b2 f8d8 d5f3 d8d3 f3e4 d3d4
167657 <first : 11 281 94 186620 h3h4 b2c2 f4f8 c6d5 f3f4 c2b2 f8d8 d5f3 d8d3 f3e4 d3g3 g6h6 g3g5 b2b4
167750 <first : 12 281 187 347225 h3h4 b2c2 f4f8 c6d5 f3f4 c2b2 f8d8 d5f3 d8d3 f3e4 d3g3 g6h6 g3g5 b2b4
<ICS: \015\012<12> -------- -------- --b---k- -------p -P---R-- -----P-P -r------ ------K- W -1 0 0 0 0 2 387 Tinker Swaminathan -1 1 0 8 9 7 2 61 K/g7-g6 (0:02) Kg6 1\015\012aics%
ics input 120, castling = -1 -1 6 -1 -1 -1
Parsing board: -------- -------- --b---k- -------p -P---R-- -----P-P -r------ ------K- W -1 0 0 0 0 2 387 Tinker Swaminathan -1 1 0 8 9 7 2 61 K/g7-g6 (0:02) Kg6 1

parseboard 120, castling = -1 -1 6 -1 -1 -1
accepted move Kg6 from ICS, parse it.
moveNum = 120
board = 0-8 x 8
move to parse: Kg6
Parser Qa1: yyleng=3, 43(-1,-1)-(6,5) = 0 ( )
Disambiguate in: 43(-1,-1)-(6,5) = 0 (-)
Disambiguate out: 43(6,6)-(6,5) = 0 (-)
CoordsToAlgebraic, piece=43 (6,6)-(6,5) -
Move parsed to 'Kg6 (0:02)'
nps: w=-1, b=-1
Display title 'Tinker (8) vs. Swaminathan (9) {1 0}, gameInfo.variant = 0'
<ICS: \007\015\012<12> -------- -------- --b---k- -------p -P---R-P -----P-- -r------ ------K- B -1 0 0 0 0 0 387 Tinker Swaminathan 1 1 0 8 9 7 2 61 P/h3-h4 (0:00) h4 1\015\012
ics input 120, castling = -1 -1 6 -1 -1 -1
Parsing board: -------- -------- --b---k- -------p -P---R-P -----P-- -r------ ------K- B -1 0 0 0 0 0 387 Tinker Swaminathan 1 1 0 8 9 7 2 61 P/h3-h4 (0:00) h4 1

parseboard 121, castling = -1 -1 6 -1 -1 -1
accepted move h4 from ICS, parse it.
moveNum = 121
board = 0-8 x 8
move to parse: h4
Disambiguate in: 0(7,-1)-(7,3) = 0 (-)
Disambiguate out: 0(7,2)-(7,3) = 0 (-)
CoordsToAlgebraic, piece=0 (7,2)-(7,3) -
-1 -1 6 -1 -1 7 Legality test? h3h4
movetype=31, promochar=0=-
Move parsed to 'h4 (0:00)'
time odds: 1 1
Interrupting first
168079 >first : time 200
168079 >first : otim 700
168079 >first : usermove 168079 >first : h3h4
nps: w=-1, b=-1
Display title 'Tinker (8) vs. Swaminathan (9) {1 0}, gameInfo.variant = 0'
<ICS: aics%
ics input 121, castling = -1 -1 6 -1 -1 -1
<ICS: Swaminathan(C) kibitzes: 14/+2.80 (11.88 sec, 2042079 nodes, 172 knps) PV = g7g6 h3h4 c6d5 g1f1 d5b7 f1e1 b7a8 e1d1 a8c6 d1c1 b2h2 c1d1 h2g2 f4f8\015\012(kibitzed to 2 people)\015\012aics%
ics input 121, castling = -1 -1 6 -1 -1 -1
168266 <first : 13 271 703 1232604 b2c2 f4f8 c6d5 f8f4 c2d2 g1f1 d2b2 f1e1 d5c6 e1d1 c6b7 d1c1 b2e2
169250 <first : 13 273 1687 2889731 c6b7 g1f1 b7a6 f1g1 a6e2 g1h1 e2b5 f4d4 g6f6 f3f4 b5c6 h1g1 f6f5 d4d6 c6e4
169266 <first : move c6b7
machine move 121, castling = -1 -1 6 -1 -1 -1
move to parse: c6b7
-1 -1 6 -1 -1 7 Legality test? c6b7
>ICS: c6b7\012
>ICS: kibitz 13/+2.73 (16.87 sec, 2889731 nodes, 171 knps) PV = c6b7 g1f1 b7a6 f1g1 a6e2 g1h1 e2b5 f4d4 g6f6 f3f4 b5c6 h1g1 f6f5 d4d6 c6e4\012
CoordsToAlgebraic, piece=24 (2,5)-(1,6) -
move: c6b7
, parse: Bb7 (
)
169282 <first : 1 250 0 1 g1f1 b7a8
169282 <first : 1 255 0 3 g1f1 b7c8
169282 <first : 1 294 0 5 g1f1 b7c6
169282 <first : 2 303 0 44 g1f1 b7c6 f1g1
169282 <first : 3 279 0 122 g1f1 b7c6 f1g1 c6b7
169282 <first : 4 314 0 339 g1f1 b7c6 f1e1 c6d5 e1f1
169282 <first : 5 282 0 637 g1f1 b7c6 f1e1 c6d5 e1f1 d5b7
169282 <first : 6 273 0 917 g1f1 b7c6 f1e1 c6d5 e1d1 d5e6 f4e4
169282 <first : 7 269 0 1519 g1f1 b7c6 f1e1 c6d5 e1d1 d5e6 d1c1 b2e2
169282 <first : 7 271 0 2708 g1f1 b7a6 f1g1 a6e2 g1h1 e2b5 f4d4 g6f6 f3f4
169282 <first : 8 266 16 13873 g1f1 b7a6 f1g1 a6e2 g1h1 e2b5 f4d4 g6f6 f3f4 b5c6 h1g1
169282 <first : 8 297 16 18011 g1f1 b7c6 f1e1 c6d5 e1d1 b2f2 f4f8 f2f3 f8f3 d5f3 d1d2
169282 <first : 9 268 16 20535 g1f1 b7c6 f1e1 c6a8 e1d1 a8b7 d1c1 b2b3 c1c2 b3f3
169297 <first : 10 279 31 39487 g1f1 b7c6 f1e1 c6d5 e1d1 d5b7 d1c1 b2b3 c1c2 b3f3 f4d4
169297 <first : 11 270 31 56106 g1f1 b7c6 f1e1 c6a8 e1d1 b2f2 f4f8 a8b7 d1c1 f2f3 f8g8 g6h7 g8g5 f3f1 c1d2
169329 <first : 11 273 62 118775 g1f1 b7a6 f1g1 a6e2 g1h1 e2b5 f4d4 g6f6 f3f4 b5c6 h1g1 f6f5 d4d6 c6e4
169375 <first : 12 279 109 185323 g1f1 b7a6 f1g1 a6e2 g1g2 e2c4 g2g3 b2b4 f4d4 b4a4 g3f4 g6f6 f4e4 c4b5 d4a4 b5c6 e4f4 c6a4
169422 <first : 13 279 156 280130 g1f1 b7a6 f1g1 a6e2 g1g2 e2c4 g2g3 b2b4 f4d4 b4a4 g3f4 g6f6 f4e4 c4b5 d4a4 b5c6 e4f4 c6a4
169563 <first : 14 279 297 566486 g1f1 b7a6 f1g1 a6e2 g1h1 e2b5 h1g1 b5c6 g1f1 c6d5 f1e1 b2h2 e1f1 h2c2 f1g1 c2d2
<ICS: \015\012<12> -------- -b------ ------k- -------p -P---R-P -----P-- -r------ ------K- W -1 0 0 0 0 1 387 Tinker Swaminathan -1 1 0 8 9 7 1 62 B/c6-b7 (0:01) Bb7 1\015\012aics%
ics input 122, castling = -1 -1 6 -1 -1 -1
Parsing board: -------- -b------ ------k- -------p -P---R-P -----P-- -r------ ------K- W -1 0 0 0 0 1 387 Tinker Swaminathan -1 1 0 8 9 7 1 62 B/c6-b7 (0:01) Bb7 1

parseboard 122, castling = -1 -1 6 -1 -1 -1
accepted move Bb7 from ICS, parse it.
moveNum = 122
board = 0-8 x 8
move to parse: Bb7
Parser Qa1: yyleng=3, 24(-1,-1)-(1,6) = 0 ( )
Disambiguate in: 24(-1,-1)-(1,6) = 0 (-)
Disambiguate out: 24(2,5)-(1,6) = 0 (-)
CoordsToAlgebraic, piece=24 (2,5)-(1,6) -
Move parsed to 'Bb7 (0:01)'
nps: w=-1, b=-1
Display title 'Tinker (8) vs. Swaminathan (9) {1 0}, gameInfo.variant = 0'
169782 <first : 15 276 516 1017262 g1f1 b7a6 f1g1 a6e2 g1h1 e2b5 h1g1 b5c6 g1f1 c6b7 f1e1 b7d5 e1f1 b2d2 f1g1 d5c6 f4f8
<ICS: Swaminathan(C) kibitzes: 13/+2.73 (16.87 sec, 2889731 nodes, 171 knps) PV = c6b7 g1f1 b7a6 f1g1 a6e2 g1h1 e2b5 f4d4 g6f6 f3f4 b5c6 h1g1 f6f5 d4d6 c6e4\015\012(kibitzed to 2 people)\015\012aics%
ics input 122, castling = -1 -1 6 -1 -1 -1
170844 <first : 16 270 1578 3027353 g1f1 b7a6 f1g1 a6e2 g1h1 e2b5 h1g1 b5c6 g1f1 c6b7 f1g1 b7d5 g1f1 d5f7 f4d4 g6f5 f1g1 f7e6
<ICS: \007\015\012<12> -------- -b------ ------k- -------p -P---R-P -----P-- -r------ -----K-- B -1 0 0 0 0 2 387 Tinker Swaminathan 1 1 0 8 9 5 1 62 K/g1-f1 (0:02) Kf1 1\015\012
ics input 122, castling = -1 -1 6 -1 -1 -1
Parsing board: -------- -b------ ------k- -------p -P---R-P -----P-- -r------ -----K-- B -1 0 0 0 0 2 387 Tinker Swaminathan 1 1 0 8 9 5 1 62 K/g1-f1 (0:02) Kf1 1

parseboard 123, castling = -1 -1 5 -1 -1 -1
accepted move Kf1 from ICS, parse it.
moveNum = 123
board = 0-8 x 8
move to parse: Kf1
Parser Qa1: yyleng=3, 21(-1,-1)-(5,0) = 0 ( )
Disambiguate in: 21(-1,-1)-(5,0) = 0 (-)
Disambiguate out: 21(6,0)-(5,0) = 0 (-)
CoordsToAlgebraic, piece=21 (6,0)-(5,0) -
Move parsed to 'Kf1 (0:02)'
time odds: 1 1
Interrupting first
171797 >first : time 100
171797 >first : otim 500
171797 >first : usermove 171797 >first : g1f1
nps: w=-1, b=-1
Display title 'Tinker (8) vs. Swaminathan (9) {1 0}, gameInfo.variant = 0'
<ICS: aics%
ics input 123, castling = -1 -1 5 -1 -1 -1
171813 <first : move b7a6
machine move 123, castling = -1 -1 5 -1 -1 -1
move to parse: b7a6
-1 -1 5 -1 -1 7 Legality test? b7a6
>ICS: b7a6\012
>ICS: kibitz 16/+2.70 (15.78 sec, 3027353 nodes, 192 knps) PV = g1f1 b7a6 f1g1 a6e2 g1h1 e2b5 h1g1 b5c6 g1f1 c6b7 f1g1 b7d5 g1f1 d5f7 f4d4 g6f5 f1g1 f7e6\012
CoordsToAlgebraic, piece=24 (1,6)-(0,5) -
move: b7a6
, parse: Ba6+ (
)
171813 <first : 1 279 0 1 f1g1 a6b7
171813 <first : 1 281 0 4 f1g1 a6b5
171813 <first : 2 270 0 47 f1g1 a6b5 f4e4
171813 <first : 2 294 0 72 f1g1 a6b7 g1f1
171813 <first : 3 294 0 135 f1g1 a6b7 g1f1 b7c6
171813 <first : 4 311 0 429 f1g1 a6b7 g1f1 b7d5 f1g1
171813 <first : 5 286 0 661 f1g1 a6b7 g1f1 b7d5 f1g1 g6h7
171813 <first : 6 280 0 1110 f1g1 a6b7 g1f1 b7d5 f1g1 g6h7 f4f5
171813 <first : 7 282 0 2217 f1g1 a6b7 g1f1 b7d5 f1g1 d5c6 g1f1 c6b7
171813 <first : 8 277 0 3949 f1g1 a6b7 g1f1 b7d5 f1e1 d5c6 e1f1 b2c2 f4f8
171813 <first : 9 271 16 10090 f1g1 a6b7 g1f1 b7a8 f1e1 a8c6 e1d1 c6b7 d1c1 b2e2
171813 <first : 9 279 16 10620 f1g1 a6e2 g1h1 e2b5 h1g1 b5c6 g1h1 b2c2 h1g1 c2a2
171813 <first : 10 276 16 13665 f1g1 a6e2 g1h1 e2b5 h1g1 b5c6 g1h1 b2c2 h1g1 c2a2 f4f8
171829 <first : 11 272 16 17723 f1g1 a6e2 g1h1 e2b5 h1g1 b5c6 g1f1 c6b7 f1e1 b7d5 e1d1 d5f7
171829 <first : 12 272 16 25450 f1g1 a6e2 g1h1 e2b5 h1g1 b5c6 g1f1 c6b7 f1g1 b7d5 g1f1 d5e6 f4d4
171829 <first : 13 273 31 47559 f1g1 a6e2 g1h1 e2b5 h1g1 b5c6 g1f1 c6b7 f1e1 b7d5 e1f1 d5e6 f4d4 g6f5
171844 <first : 14 271 47 79440 f1g1 a6e2 g1h1 e2b5 h1g1 b5c6 g1f1 c6b7 f1e1 b7d5 e1f1 b2c2 f4f8 c2h2 b4b5 h2h4
171985 <first : 15 270 188 359948 f1g1 a6e2 g1h1 e2b5 h1g1 b5c6 g1f1 c6b7 f1e1 b7d5 e1f1 d5f7 f4d4 g6f5 f1g1 f7e6
172438 <first : 16 280 641 1206155 f1g1 a6e2 g1h1 e2b5 h1g1 b5c6 g1f1 c6b7 f1e1 b7d5 e1d1 d5c6 d1c1 b2h2 c1d1 h2g2 f4f8
<ICS: \015\012<12> -------- -------- b-----k- -------p -P---R-P -----P-- -r------ -----K-- W -1 0 0 0 0 3 387 Tinker Swaminathan -1 1 0 8 9 5 1 63 B/b7-a6 (0:00) Ba6+ 1\015\012aics%
ics input 124, castling = -1 -1 5 -1 -1 -1
Parsing board: -------- -------- b-----k- -------p -P---R-P -----P-- -r------ -----K-- W -1 0 0 0 0 3 387 Tinker Swaminathan -1 1 0 8 9 5 1 63 B/b7-a6 (0:00) Ba6+ 1

parseboard 124, castling = -1 -1 5 -1 -1 -1
accepted move Ba6+ from ICS, parse it.
moveNum = 124
board = 0-8 x 8
move to parse: Ba6+
Parser Qa1: yyleng=3, 24(-1,-1)-(0,5) = 0 ( )
Disambiguate in: 24(-1,-1)-(0,5) = 0 (-)
Disambiguate out: 24(1,6)-(0,5) = 0 (-)
CoordsToAlgebraic, piece=24 (1,6)-(0,5) -
Move parsed to 'Ba6+ (0:00)'
nps: w=-1, b=-1
Display title 'Tinker (8) vs. Swaminathan (9) {1 0}, gameInfo.variant = 0'
<ICS: Swaminathan(C) kibitzes: 16/+2.70 (15.78 sec, 3027353 nodes, 192 knps) PV = g1f1 b7a6 f1g1 a6e2 g1h1 e2b5 h1g1 b5c6 g1f1 c6b7 f1g1 b7d5 g1f1 d5f7 f4d4 g6f5 f1g1 f7e6\015\012(kibitzed to 2 people)\015\012aics%
ics input 124, castling = -1 -1 5 -1 -1 -1
173250 <first : 17 274 1453 2784515 f1g1 a6e2 g1h1 e2b5 h1g1 b5c6 g1f1 c6b7 f1e1 b7d5 e1d1 d5c6 d1c1 b2h2 c1d1 h2g2 d1c1 c6b5
<ICS: \007\015\012<12> -------- -------- b-----k- -------p -P---R-P -----P-- -r------ ----K--- B -1 0 0 0 0 4 387 Tinker Swaminathan 1 1 0 8 9 4 1 63 K/f1-e1 (0:01) Ke1 1\015\012
ics input 124, castling = -1 -1 5 -1 -1 -1
Parsing board: -------- -------- b-----k- -------p -P---R-P -----P-- -r------ ----K--- B -1 0 0 0 0 4 387 Tinker Swaminathan 1 1 0 8 9 4 1 63 K/f1-e1 (0:01) Ke1 1

parseboard 125, castling = -1 -1 4 -1 -1 -1
accepted move Ke1 from ICS, parse it.
moveNum = 125
board = 0-8 x 8
move to parse: Ke1
Parser Qa1: yyleng=3, 21(-1,-1)-(4,0) = 0 ( )
Disambiguate in: 21(-1,-1)-(4,0) = 0 (-)
Disambiguate out: 21(5,0)-(4,0) = 0 (-)
CoordsToAlgebraic, piece=21 (5,0)-(4,0) -
Move parsed to 'Ke1 (0:01)'
time odds: 1 1
Interrupting first
173969 >first : time 100
173969 >first : otim 400
173969 >first : usermove 173969 >first : f1e1
nps: w=-1, b=-1
Display title 'Tinker (8) vs. Swaminathan (9) {1 0}, gameInfo.variant = 0'
<ICS: aics%
ics input 125, castling = -1 -1 4 -1 -1 -1
173969 <first : 1 283 0 1 a6b7
173969 <first : 2 294 0 101 a6b7 e1f1
173969 <first : 3 297 0 198 a6b7 e1d1 b7c6
173985 <first : 4 311 0 428 a6b7 e1f1 b7d5 f1g1
173985 <first : 5 284 0 740 a6b7 e1f1 b7d5 f1g1 b2c2
173985 <first : 6 280 0 1585 a6b7 e1f1 b7d5 f1g1 b2c2 f4f8
173985 <first : 7 280 0 2708 a6b7 e1f1 b7d5 f1g1 b2c2 g1f1 d5c6
173985 <first : 8 277 0 4762 a6b7 e1f1 b7d5 f1g1 b2c2 g1f1 d5c6 f4f8
173985 <first : 8 284 0 11946 a6e2 e1f2 e2c4 f2g3 b2b4 f4e4 b4a4 e4d4 c4b3
173985 <first : 9 277 16 17976 a6e2 e1f2 e2c4 f2e3 b2b4 f4d4 b4b3 e3e4 c4e6 e4e5 b3b6
174000 <first : 10 282 31 50293 a6e2 e1f2 e2c4 f2g3 b2b4 f4e4 b4a4 g3f4 c4b5 e4a4 b5a4
174016 <first : 11 285 47 81532 a6e2 e1f2 e2c4 f2g3 b2b4 f4e4 b4a4 f3f4 a4a3 g3f2 c4d3 e4e6 g6f5 e6e5 f5g4
174047 <first : 12 286 78 130124 a6e2 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 d4e4 g6f6 e4f4 f6g7 f4f5 c4f7 f3f4
174063 <first : 13 282 94 171478 a6e2 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 d4e4 g6f6 e4f4 f6g7 f4f5 c4f7 f3f4 a4a3 g3g2
174172 <first : 14 279 203 376579 a6e2 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 d4e4 c4b3 e4e5 a4a1 e5b5 b3c4 b5g5 g6h6 f3f4 a1a3 g3g2
174454 <first : 15 284 484 904101 a6e2 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 d4e4 c4b3 e4e3 b3d5 e3e5 a4d4 e5g5 g6h6 f3f4 d4d3 g3h2
175235 <first : 16 289 1266 2268427 a6e2 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 d4e4 c4b5 e4e5 b5d7 e5g5 g6h6 f3f4 a4a3 g3f2 d7c6 f2e2 a3f3
175579 <first : move a6e2
machine move 125, castling = -1 -1 4 -1 -1 -1
move to parse: a6e2
-1 -1 4 -1 -1 7 Legality test? a6e2
>ICS: a6e2\012
>ICS: kibitz 16/+2.89 (12.66 sec, 2268427 nodes, 179 knps) PV = a6e2 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 d4e4 c4b5 e4e5 b5d7 e5g5 g6h6 f3f4 a4a3 g3f2 d7c6 f2e2 a3f3\012
CoordsToAlgebraic, piece=24 (0,5)-(4,1) -
move: a6e2
, parse: Be2 (
)
175594 <first : 1 233 0 8 e1f2 e2d3 f2e3
175594 <first : 1 245 0 28 e1f2 e2b5 f2g3
175594 <first : 1 285 0 55 e1f2 e2c4 f2g3 b2b4
175594 <first : 2 285 0 86 e1f2 e2c4 f2g3 b2b4
175594 <first : 3 281 0 256 e1f2 e2c4 f2g3 b2b4 f4d4
175594 <first : 4 281 16 550 e1f2 e2c4 f2g3 b2b4 f4d4 g6f5
175594 <first : 5 281 16 853 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 d4e4
175594 <first : 6 289 16 1225 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 d4e4 c4b5
175594 <first : 7 282 16 2148 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 g3f4 c4b3 d4a4 b3a4
175594 <first : 8 282 16 4036 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 g3f4 c4b3 d4a4 b3a4
175594 <first : 9 279 16 8824 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 g3f4 g6f6 f4e4 c4b5 d4a4 b5c6 e4f4 c6a4
175594 <first : 10 286 16 14707 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 d4e4 c4b5 e4e5 b5d3 e5g5 g6h6 f3f4
175610 <first : 11 279 16 26357 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 d4e4 c4b3 e4e5 a4a1 f3f4 a1f1 e5g5 g6h6
175610 <first : 12 285 32 47033 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 d4e4 c4b3 e4e5 a4a1 g3f4 a1f1 e5g5 g6h6 g5b5
175610 <first : 13 285 32 82336 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 d4e4 c4b5 e4e5 b5d7 e5g5 g6h6 f3f4 a4a3 g3f2 d7c6 f2e2
175641 <first : 14 289 63 141574 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 d4e4 c4b5 e4e5 b5d7 e5g5 g6h6 f3f4 a4a3 g3f2 d7c6 f2e2 a3f3
175782 <first : 15 283 204 445304 e1f2 e2c4 f2g3 b2b4 f4d4 b4a4 d4e4 c4b5 e4e5 b5d3 e5g5 g6h6 f3f4 d3e4 g5e5 a4b4 e5e6 h6g7 e6e7 g7f6
<ICS: \007\015\012<12> -------- -------- b-----k- -------p -P---R-P -----P-- -r------ ----K--- B -1 0 0 0 0 4 387 Tinker Swaminathan 1 1 0 8 9 4 -1 63 K/f1-e1 (0:01) Ke1 1\015\012{Game 387 (Tinker vs. Swaminathan) Swaminathan forfeits on time} 1-0\015\012Game was not rated. No rating adjustment.\015\012No such command (a6e2).\015\012aics%
ics input 126, castling = -1 -1 4 -1 -1 -1
Parsing board: -------- -------- b-----k- -------p -P---R-P -----P-- -r------ ----K--- B -1 0 0 0 0 4 387 Tinker Swaminathan 1 1 0 8 9 4 -1 63 K/f1-e1 (0:01) Ke1 1

parseboard 125, castling = -1 -1 4 -1 -1 -1
accepted move Ke1 from ICS, parse it.
moveNum = 125
board = 0-8 x 8
move to parse: Ke1
Parser Qa1: yyleng=3, 21(-1,-1)-(4,0) = 0 ( )
Disambiguate in: 21(-1,-1)-(4,0) = 0 (-)
Disambiguate out: 21(5,0)-(4,0) = 0 (-)
CoordsToAlgebraic, piece=21 (5,0)-(4,0) -
Move parsed to 'Ke1 (0:01)'
nps: w=-1, b=-1
Display title 'Tinker (8) vs. Swaminathan (9) {1 0}, gameInfo.variant = 0'
GameEnds(35, Swaminathan forfeits on time, 0)
GameEnds(35, Swaminathan forfeits on time, 0) clock stopped
GameEnds(35, Swaminathan forfeits on time, 0) after test
Interrupting first
175969 >first : result 1-0 {Swaminathan forfeits on time}
175969 >first : force
175969 >first : ping 2
>ICS: gameend\012
>ICS: \012
Reset(1, 1) from gameMode 11
recognized 'normal' (-1) as variant normal
GameEnds(0, (null), 2)
GameEnds(0, (null), 2) clock stopped
GameEnds(0, (null), 2) after test
shuffleOpenings = 0
175985 >first : new
random
175985 >first : ics chessclub.com
175985 >first : post
175985 >first : hard
175985 >first : ping 3
175985 <first : pong 2
175985 <first : pong 3
<ICS: You are not observing or playing in any games.\015\012aics%
ics input 0, castling = 7 0 4 7 0 4
<ICS: No such command (gameend).\015\012aics%
ics input 0, castling = 7 0 4 7 0 4
Fatal Error: Error: first chess program (bright) exited unexpectedly
GameEnds(36, Error: first chess program (bright) exited unexpectedly, 2)
GameEnds(36, Error: first chess program (bright) exited unexpectedly, 2) clock stopped
GameEnds(36, Error: first chess program (bright) exited unexpectedly, 2) after test
182188 >first : result 0-1 {Error: first chess program (bright) exited unexpectedly}
182188 >first : force
182188 >first : ping 4
182188 >first : quit

[hgm]

It seems that Bright only crashes in the next game after the one it forfeited on time. It still replies to the ping 3 it was sent after the new with a pong 3, so at that time it must still have been alive.

It seems Bright simply forfeits on time: on the last move WB sends it (f1e1) it was told it still had 100 csec on the clock (time 100). In the search that follows, it simply lets the time run up to 203 centi-sec (after iteration 14). Well, if you have only 100 csec, and then think for 203 csec, you forfeit. That is how Chess clocks work. I don't see any irregularities in the communication between engine and GUI...

[swami]

It seems that Bright only crashes in the next game after the one it forfeited on time. It still replies to the ping 3 it was sent after the new with a pong 3, so at that time it must still have been alive.

It seems Bright simply forfeits on time: on the last move WB sends it (f1e1) it was told it still had 100 csec on the clock (time 100). In the search that follows, it simply lets the time run up to 203 centi-sec (after iteration 14). Well, if you have only 100 csec, and then think for 203 csec, you forfeit. That is how Chess clocks work. I don't see any irregularities in the communication between engine and GUI...

Well, With chess Partner, It doesn't forfeit on time at all. I have let Bright play hundreds of games, and it's not lost a single game on time.

In test games offline, It didn't forfeit either. Rather a strange bug it has when it's made to play under winboard?

[hgm]

Indeed, I have no idea why this should behave different under WinBoard and not under Chess Partner. But it is clear that it uses more time than WinBoard tells it that it has (in a way fully compliant with WB protocol), and this by definition is a fault of the engine. Perhaps Chess Partner adds a safety margin to the time, so that even if Bright forfeits the time specified by the GUI, it does not not forfeit the time originally specified by the ICS. Who knows? Impossible to say without seeing a similar debug trace for Bright running under Chess Partner.

One thing is sure, though: WB does send it the correct time, as the ICS specified (1 sec and 4 sec), and the engine exceeds it.

That it crashes later, after starting a new game, is also suspicious. When exactly does this popup saying Bright has crashed appear? If Bright is multi-threaded, it could be that oone of its threads crashed much earlier, and that the other threads just make it play on (but do not check the time).

[Dr.Wael Deeb]

I can confirm also that Bright hasn't lost a game on time running offline under the Arena GUI....

[swami]

That it crashes later, after starting a new game, is also suspicious. When exactly does this popup saying Bright has crashed appear? If Bright is multi-threaded, it could be that oone of its threads crashed much earlier, and that the other threads just make it play on (but do not check the time).

Actually, I think it crashes in the first game itself. Just after I log in, challenge, let it play the first game, Play for certain number of moves, then It crashes. Loses on time more often. Exits sometimes, other times It doesn't exit.

Your last reasoning about the allocation of cores and one of the threads crashed could be plausible. I use 4 cores for Bright. It doesn't crash when the game ends in three fold repetition. How could I verify if one thread malfunction crashed it?

I'm not sure how I could find the debug file from Chess Partner. There are so many files in that folder.

The pop up box that Bright has crashed appear after it loses on time.

[hgm]

OK, the latter information is very important. That makes it very unlikely that Bright forfeits because of the crash.

I think this is a problem that only Allard can solve. I do not see anything unusual WB sends to bright that could make it crash before the time forfeit. Just the normal time, otim and usermove commands. If it crashes on a command that Chess Partner sends in a different order then WinBoard, that must have happened in the very beginning of the game, then.

[Allard Siemelink]

Yup, this is a bug in Bright's (experimental) Winboard protocol handling code. I'll get it fixed in the next release.

The loss on time is easily explained: Bright simply does not respond to the time command at all!
Instead, it relies on the level command, which appearantly gets sent only on the start of the game, not on every move.
So I guess Bright should recalculate the search time on each move by remembering the last level command, but compensate for the actual time left according to ' time ' and moves left according to the board.

btw, how should the movenr of a fen string be taken into account?
(e.g. I get a fen that says 39 moves have been played, will the level command will tell me the time control is 40 moves/40 minutes, meaning I have 40 minutes for the 40th move? or should we start counting from the current move as the first move?

The crashing may be caused by winboard sending a newgame command while bright is still calculating (destroying the board).
Although the spec does not mention it, I guess Bright should stop calculating on either or all of the 'result', ' force' and 'newgame' commands...
What is best practise here?

btw, hgm, you're correct that the pongs are sent from the gui threat, so this is regardless of the state of any search threads.

OK, the latter information is very important. That makes it very unlikely that Bright forfeits because of the crash.

I think this is a problem that only Allard can solve. I do not see anything unusual WB sends to bright that could make it crash before the time forfeit. Just the normal time, otim and usermove commands. If it crashes on a command that Chess Partner sends in a different order then WinBoard, that must have happened in the very beginning of the game, then.

[hgm]

These are good questions.

Logical thing would be to believe the move number in the FEN. I should add, though, that WinBoard only ever sends FENs (in setboard commands) to an engine at the beginning of a game (if at all). Any pasting of a FEN or use of the edit-position menu in WinBoard triggers the start of new game. And that new game starts counting at move 1. All WinBoards so far ignore the move number in FENs that you paste into them, and reset the move number to 1 in stead. As a consequence, it also only sends FENs with move number 1 to an engine, although its FEN writer does use the GUI internal move count in the move number field (e.g. when you paste a FEN to the clipboard).

This is an undesirable situation, and I think it would be better if WinBoard would actually conform its internal move count (determining when time-control sessions start) to any FENs pasted into it, and inform the engine accordingly in the startup FEN. But I have no idea how many engines this would break... Engines do have to know how many moves they have to last with the current clock reading.

So my advice: let Bright pay attention to the FEN move number, if it is 39, and you play level 40 5 0, and receive time 30000, you can take 5 min for the next move. (But probably smarter would be to act as if you would have 10 min for 41 moves.

Indeed new, force and RESULT should all terminate pondering and also searching. But the most important thing is that, if you can't do that immediately, you should not send frivolous pongs. Pong really means that you have fully processed all previous commands. So WB would never send you the new if you did not answer the ping it sent after the RESULT command first. Sending pongs too early, even if your engine would only implement the new when it was ready, could lead to starting your clock too early.[/b]

[Allard Siemelink]

thanks for the explanation, I'll keep it simple for now as I find it more important to solve the crash, so i will always assume move 1 from the fen for now.

Fortunately, once new, force and result actually will stop the search, the pong should pose no problem as stopping the search will wait for the main search thread to exit the search.
(the smp threads do not matter as they have their own boards which they'll synchronize themselves once they start a new search.
Hmm, come to think of it, the master search thread has it's own board too, so I am not so sure anymore why it crashed...)