First Engine Exited Unexpectedly

[YNODE]

Hi,

I am having a very strange case/bug with my engine while playing on FICS through Winboard(4.8.x) This case happens very rarely. But once this happens my engine stops playing on FICS. After some time, my session is killed by FICS for being too idle.

Problem:
During a search, when PV lines start to get longer Winboard raises a strange error. "First engine exited unexpectedly". This happens almost always at depths more than 15. Strangely, when i check logs of my own, i can see that the engine is still running and sending think lines for deeper depths to Winboard. Somehow, Winboard does not care about later think lines and thinks my engine exited.

When this case happens, i send "go" command to my engine from commmand ilne and it starts to think again. But no luck, winboard does not care about the think lines.

When i close poped up error messagebox that Winboard raised then Winboard sends "quit" message to my engine and after a few seconds kills my engine.

After lots of debugging, i started to think that this is an Winboard bug.
Did anyone face with this case previously ?

Your comments are welcome.

Orhan

[Ferdy]

Hi,

I am having a very strange case/bug with my engine while playing on FICS through Winboard(4.8.x) This case happens very rarely. But once this happens my engine stops playing on FICS. After some time, my session is killed by FICS for being too idle.

Problem:
During a search, when PV lines start to get longer Winboard raises a strange error. "First engine exited unexpectedly". This happens almost always at depths more than 15. Strangely, when i check logs of my own, i can see that the engine is still running and sending think lines for deeper depths to Winboard. Somehow, Winboard does not care about later think lines and thinks my engine exited.

When this case happens, i send "go" command to my engine from commmand ilne and it starts to think again. But no luck, winboard does not care about the think lines.

When i close poped up error messagebox that Winboard raised then Winboard sends "quit" message to my engine and after a few seconds kills my engine.

After lots of debugging, i started to think that this is an Winboard bug.
Did anyone face with this case previously ?

Your comments are welcome.

Orhan

Could you post the relevant winboard log and your engine's log?

[hgm]

This error message is triggered in WinBoard when reading from the pipe connecting it with the engine returns an end-of-file result. This should only happen when the engine somehow closes that pipe (usually by exiting).

Considering that many people are running their engines through WinBoard all the time, and never experience this error message, it does seem unlikely that it is a WinBoard bug. At the very least it must be related to something your engine does. It cannot be excluded completely that WinBoard starts to do random things (including sending a spurious error message) when it is crashing for other reasons.

It would be helpful if you could run WinBoard with the extra option /debug , and post the last part of the winboard.debug file it created on a run where this problem occurred here,

[sje]

I had a problem something like this is a long-ago version of XBoard. I resolved the issue by limiting the length of the strings sent to XBoard, reporting only the first five or so moves of the predicted variation. Give that a try and see what happens.

[hgm]

I remember that it was indeed a problem that the buffer for holding the PV at some stage could overflow, and crash Win/XBoard. But this should have neen fixed by (clipping the PV to a safe length before further processing it). I don't believe the low-level input buffers can overflow. Current engines often spit out PVs of 40 moves or more, and if this was a problem, we would have surely known by now.

[bob]

I had a problem something like this is a long-ago version of XBoard. I resolved the issue by limiting the length of the strings sent to XBoard, reporting only the first five or so moves of the predicted variation. Give that a try and see what happens.

This is not a problem today. Crafty produces PVs with up to 128 actual moves, plus the move numbers, and xboard has no problems at all...

[YNODE]

After more than 50 games, finally i re-produced the case.

The position in the game: 8/1r5k/4p3/8/p1p4P/P7/1P3P2/1K3N2 b
Winboard version: 4.8.0b

At depth 15, Winboard popped up a message saying "first engine exited unexpectedly" whereas my engine was still up and it was searching...

Winboard Log with debug parameter (Depth 11-14)
----------------------------------------------------------------------
1444941 <first : 11 301 14 27505 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[2][H2] 6) d3e2[1][H2] - f4h4[1][H2]
Impossible move f4h4, type = 0
1444953 <first : 11 301 15 44656 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[2][H2] 6) d3e2[1][H2] - f4h4[1][H2]
Impossible move f4h4, type = 0
1444964 <first : 12 301 16 50479 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[1][H1] 6) d3e2[1][H1] - f4h4[1][H1] 7) d2f3[1][H2] - ......
Impossible move d2f3, type = 0
1444979 <first : 12 301 18 68389 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[1][H1] 6) d3e2[1][H1] - f4h4[1][H1] 7) d2f3[1][H2] - ......
Impossible move d2f3, type = 0
1444992 <first : 13 301 19 81993 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - f4h4[2] 6) d2f3[1][H2] - h4g4[6] 7) d3d2[1][H2] - h7g8[5]
Impossible move h7g8, type = 0
1445018 <first : 13 301 22 126046 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - f4h4[2] 6) d2f3[1][H2] - h4g4[6] 7) d3d2[1][H2] - h7g8[5]
Impossible move h7g8, type = 0
1445025 <first : 14 302 22 127129 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[2][H2] 6) d3e2[1][H2] - f4h4[1][H2] 7) d2f3[1][H2] - h4h1[1][H2] 8) f3d4[1][H2] - ......
Impossible move f3d4, type = 0
Fatal Error: Error: first chess program (YnodeC_0028 WinBoard) exited unexpectedly


My Engine's log (The messages sent to Winboard while searching)
----------------------------------------------------------------------
23:28:57 11 301 14 27505 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[2][H2] 6) d3e2[1][H2] - f4h4[1][H2]
23:28:57 11 301 15 44656 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[2][H2] 6) d3e2[1][H2] - f4h4[1][H2]
23:28:57 12 301 16 50479 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[1][H1] 6) d3e2[1][H1] - f4h4[1][H1] 7) d2f3[1][H2] - ......
23:28:57 12 301 18 68389 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[1][H1] 6) d3e2[1][H1] - f4h4[1][H1] 7) d2f3[1][H2] - ......
23:28:57 13 301 19 81993 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - f4h4[2] 6) d2f3[1][H2] - h4g4[6] 7) d3d2[1][H2] - h7g8[5]
23:28:57 13 301 22 126046 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - f4h4[2] 6) d2f3[1][H2] - h4g4[6] 7) d3d2[1][H2] - h7g8[5]
23:28:57 14 302 22 127129 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[2][H2] 6) d3e2[1][H2] - f4h4[1][H2] 7) d2f3[1][H2] - h4h1[1][H2] 8) f3d4[1][H2] - ......
23:28:57 14 302 23 127162 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[2][H2] 6) d3e2[1][H2] - f4h4[1][H2] 7) d2f3[1][H2] - h4h1[1][H2] 8) f3d4[1][H2] - ......
23:28:58 15 300 56 755574 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[1][H1] 6) d3e3[9] - f4h4[1][H2] 7) d2f3[1][H2] - h4h7[1][H2] 8) e3d3[1][H2] - h7h8[1][H2]
23:28:58 15 300 71 1046350 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[1][H1] 6) d3e3[9] - f4h4[1][H2] 7) d2f3[1][H2] - h4h7[1][H2] 8) e3d3[1][H2] - h7h8[1][H2]
23:28:59 16 300 124 2070000 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[1][H1] 6) d3e3[9] - f4h4[1][H2] 7) d2f3[1][H2] - h4h7[1][H2] 8) e3d3[1][H2] - h7h8[1][H2]
23:28:59 move c4c3

Actually, my engine searched up to depth=16, even Winboard claims it exited.

PS:
1 - The brackets after moves, just for information to myself, hash usage, move order etc...
2 - Winboard also claims there is some illegal moves in the path that is posted by engine, even they are completely legal.

I hope you can suggest me something to fix it.

Orhan Öztürk

[bob]

After more than 50 games, finally i re-produced the case.

The position in the game: 8/1r5k/4p3/8/p1p4P/P7/1P3P2/1K3N2 b
Winboard version: 4.8.0b

At depth 15, Winboard popped up a message saying "first engine exited unexpectedly" whereas my engine was still up and it was searching...

Winboard Log with debug parameter (Depth 11-14)
----------------------------------------------------------------------
1444941 <first : 11 301 14 27505 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[2][H2] 6) d3e2[1][H2] - f4h4[1][H2]
Impossible move f4h4, type = 0
1444953 <first : 11 301 15 44656 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[2][H2] 6) d3e2[1][H2] - f4h4[1][H2]
Impossible move f4h4, type = 0
1444964 <first : 12 301 16 50479 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[1][H1] 6) d3e2[1][H1] - f4h4[1][H1] 7) d2f3[1][H2] - ......
Impossible move d2f3, type = 0
1444979 <first : 12 301 18 68389 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[1][H1] 6) d3e2[1][H1] - f4h4[1][H1] 7) d2f3[1][H2] - ......
Impossible move d2f3, type = 0
1444992 <first : 13 301 19 81993 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - f4h4[2] 6) d2f3[1][H2] - h4g4[6] 7) d3d2[1][H2] - h7g8[5]
Impossible move h7g8, type = 0
1445018 <first : 13 301 22 126046 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - f4h4[2] 6) d2f3[1][H2] - h4g4[6] 7) d3d2[1][H2] - h7g8[5]
Impossible move h7g8, type = 0
1445025 <first : 14 302 22 127129 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[2][H2] 6) d3e2[1][H2] - f4h4[1][H2] 7) d2f3[1][H2] - h4h1[1][H2] 8) f3d4[1][H2] - ......
Impossible move f3d4, type = 0
Fatal Error: Error: first chess program (YnodeC_0028 WinBoard) exited unexpectedly


My Engine's log (The messages sent to Winboard while searching)
----------------------------------------------------------------------
23:28:57 11 301 14 27505 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[2][H2] 6) d3e2[1][H2] - f4h4[1][H2]
23:28:57 11 301 15 44656 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[2][H2] 6) d3e2[1][H2] - f4h4[1][H2]
23:28:57 12 301 16 50479 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[1][H1] 6) d3e2[1][H1] - f4h4[1][H1] 7) d2f3[1][H2] - ......
23:28:57 12 301 18 68389 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[1][H1] 6) d3e2[1][H1] - f4h4[1][H1] 7) d2f3[1][H2] - ......
23:28:57 13 301 19 81993 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - f4h4[2] 6) d2f3[1][H2] - h4g4[6] 7) d3d2[1][H2] - h7g8[5]
23:28:57 13 301 22 126046 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - f4h4[2] 6) d2f3[1][H2] - h4g4[6] 7) d3d2[1][H2] - h7g8[5]
23:28:57 14 302 22 127129 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[2][H2] 6) d3e2[1][H2] - f4h4[1][H2] 7) d2f3[1][H2] - h4h1[1][H2] 8) f3d4[1][H2] - ......
23:28:57 14 302 23 127162 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[2][H2] 6) d3e2[1][H2] - f4h4[1][H2] 7) d2f3[1][H2] - h4h1[1][H2] 8) f3d4[1][H2] - ......
23:28:58 15 300 56 755574 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[1][H1] 6) d3e3[9] - f4h4[1][H2] 7) d2f3[1][H2] - h4h7[1][H2] 8) e3d3[1][H2] - h7h8[1][H2]
23:28:58 15 300 71 1046350 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[1][H1] 6) d3e3[9] - f4h4[1][H2] 7) d2f3[1][H2] - h4h7[1][H2] 8) e3d3[1][H2] - h7h8[1][H2]
23:28:59 16 300 124 2070000 1) ...... - c4c3[1][H1] 2) b1c2[1][H1] - b7b2[1][H1] 3) c2c3[1][H1] - b2f2[1][H1] 4) f1d2[1][H1] - f2f4[1][H1] 5) c3d3[1][H1] - h7g6[1][H1] 6) d3e3[9] - f4h4[1][H2] 7) d2f3[1][H2] - h4h7[1][H2] 8) e3d3[1][H2] - h7h8[1][H2]
23:28:59 move c4c3

Actually, my engine searched up to depth=16, even Winboard claims it exited.

PS:
1 - The brackets after moves, just for information to myself, hash usage, move order etc...
2 - Winboard also claims there is some illegal moves in the path that is posted by engine, even they are completely legal.

I hope you can suggest me something to fix it.

Orhan Öztürk

You probably should not send so much garbage to winboard. I don't know what the actual limit on what can be sent, but in general the crap probably should be sent to your log but not to the pipe. I'd be concerned if "h1" became a legal move, for example. But with all the special characters, picking moves out is a challenge.

HGM can tell you whether that is a problem.

[sje]

I had a problem something like this is a long-ago version of XBoard. I resolved the issue by limiting the length of the strings sent to XBoard, reporting only the first five or so moves of the predicted variation. Give that a try and see what happens.

This is not a problem today. Crafty produces PVs with up to 128 actual moves, plus the move numbers, and xboard has no problems at all...

Apparently so, as in the current testing, Symbolic posted a MateIn54 PV (107 moves) and XBoard handled it properly.

The longest PV produced by Symbolic so far has 247 moves:
[d]8/2Q4K/8/1q6/8/3P4/8/7k w - - 0 1[/d]
1. Qc3 Qg5 2. Kh8 Qe7 3. Kg8 Qe8+ 4. Kg7 Qe7+ 5. Kg6 Qe6+ 6. Kg5 Qe3+ 7. Kf5 Kg2 8. Qc4 Qf3+ 9. Kg6 Qg3+ 10. Kf7 Qf2+ 11. Ke7 Qa7+ 12. Ke6 Qb6+ 13. Kf5 Qf2+ 14. Qf4 Qc5+ 15. Qe5 Qf8+ 16. Qf6 Qc5+ 17. Ke4 Qc2 18. Qd4 Kf1 19. Kd5 Qa2+ 20. Kd6 Qg8 21. Kc7 Qf7+ 22. Qd7 Qf4+ 23. Qd6 Qf7+ 24. Kc6 Qf3+ 25. Qd5 Qf6+ 26. Kd7 Qg7+ 27. Ke8 Qh8+ 28. Ke7 Qh4+ 29. Kd7 Qa4+ 30. Kd6 Qf4+ 31. Qe5 Qf8+ 32. Kc7 Qf7+ 33. Kc6 Qf3+ 34. Qe4 Qf8 35. Kb7 Qf7+ 36. Ka6 Qa2+ 37. Kb5 Qb2+ 38. Kc4 Qa2+ 39. Kd4 Qb2+ 40. Kd5 Qb5+ 41. Kd6 Qb8+ 42. Ke7 Qc7+ 43. Ke6 Qc8+ 44. Kf7 Qc7+ 45. Kg6 Qg3+ 46. Kf6 Qd6+ 47. Kf5 Qf8+ 48. Kg4 Qg7+ 49. Kf3 Qf6+ 50. Qf4 Qc3 51. Ke4+ Ke2 52. Qe3+ Kd1 53. d4 Qc6+ 54. Kf5 Qd7+ 55. Kg6 Qd6+ 56. Kh5 Qd5+ 57. Qe5 Qf3+ 58. Kg5 Qg2+ 59. Kf6 Qa8 60. Qc5 Qd8+ 61. Kf5 Qd7+ 62. Kf4 Qf7+ 63. Qf5 Qc4 64. Qe4 Qc7+ 65. Kf3 Qc3+ 66. Kg2 Qb2+ 67. Kg1 Qb6 68. Qd3+ Ke1 69. Qe3+ Kd1 70. Kf2 Qa7 71. Qd3+ Kc1 72. Ke3 Qe7+ 73. Qe4 Qg5+ 74. Kf2 Qf6+ 75. Ke2 Qa6+ 76. Kf3 Qf1+ 77. Kg4 Qc4 78. Kf4 Qf7+ 79. Qf5 Qg7 80. d5 Qd4+ 81. Kg5 Qg7+ 82. Kh4 Qc7 83. Kg4 Kd1 84. Qd3+ Kc1 85. Qd4 Qc8+ 86. Kf4 Qf8+ 87. Ke4 Qa8 88. Kd3 Qa3+ 89. Qc3+ Kb1 90. Kd4 Qa4+ 91. Ke3 Qd7 92. Qc6 Qa7+ 93. Kd3 Qa3+ 94. Kc4 Qa2+ 95. Kb5 Qb2+ 96. Ka5 Qa3+ 97. Kb6 Qe3+ 98. Qc5 Qb3+ 99. Kc7 Ka1 100. Qd4+ Ka2 101. d6 Qg3 102. Kb6 Qb3+ 103. Ka5 Qg8 104. Qa4+ Kb1 105. Qb5+ Kc1 106. d7 Qd8+ 107. Ka6 Qa8+ 108. Kb6 Qb8+ 109. Kc6 Qa8+ 110. Kc7 Qa7+ 111. Qb7 Qa5+ 112. Qb6 Qe5+ 113. Kb7 Qe7 114. Qc7+ Kb1 115. d8=Q Qe4+ 116. Qc6 Qb4+ 117. Ka6 Qa3+ 118. Qa5 Kb2 119. Qb5+ Ka2 120. Qxa3+ Kxa3 121. Ka5 Ka2 122. Ka4 Ka1 123. Kb3 Kb1 124. Qf1#

[sje]

Two suggestions:

1) Remove unnecessary output like "[1][H2]" for better readability. Do not assume that XBoard is ignoring extraneous output.

2) Use XBoard's debug feature to send strings to XBoard which it will echo in its log. Before posting a PV, first send it as a debug comment so you can verify that XBoard is really getting what is being sent.