First, I mis-reported the game count; it is now 332 games.hgm wrote:Hmm, let's hope not.
The battle is still going with no sign of any bug.
The debug file:
Code: Select all
$ wc xboard.debug
890154 5910433 32006019 xboard.debug
Moderator: Ras
First, I mis-reported the game count; it is now 332 games.hgm wrote:Hmm, let's hope not.
Code: Select all
$ wc xboard.debug
890154 5910433 32006019 xboard.debug
Does it hang on FICS without -debug?sje wrote:First, I mis-reported the game count; it is now 332 games.hgm wrote:Hmm, let's hope not.
The battle is still going with no sign of any bug.
The debug file:Code: Select all
$ wc xboard.debug 890154 5910433 32006019 xboard.debug
Yes sometimes with the unexpected "undo" command same as ICC.bob wrote:Does it hang on FICS without -debug?sje wrote:First, I mis-reported the game count; it is now 332 games.hgm wrote:Hmm, let's hope not.
The battle is still going with no sign of any bug.
The debug file:Code: Select all
$ wc xboard.debug 890154 5910433 32006019 xboard.debug
It might be ICC related, somehow...
After 492 games, it's starting to look like activating the xboard debug output deactivates both the modify-after-free bug and the bad undo bug.hgm wrote:Hmm, let's hope not.
Code: Select all
$ wc xboard.debug
1306493 8732196 47297515 xboard.debug
Bob (and others) had problems on FICS at CCT time controls. Maybe he could test his setup over there again with debug to see of the problem goes away.sje wrote:After 492 games, it's starting to look like activating the xboard debug output deactivates both the modify-after-free bug and the bad undo bug.hgm wrote:Hmm, let's hope not.Code: Select all
$ wc xboard.debug 1306493 8732196 47297515 xboard.debug
I don't think that the time control has much to do with either bug, but I could be wrong. The bad-undo bug seems to be strongly linked to an out-of-turn opponent resignation; this may have a timing component, but not one related to the chess clock.mhull wrote:Bob (and others) had problems on FICS at CCT time controls. Maybe he could test his setup over there again with debug to see of the problem goes away.sje wrote:After 492 games, it's starting to look like activating the xboard debug output deactivates both the modify-after-free bug and the bad undo bug.hgm wrote:Hmm, let's hope not.Code: Select all
$ wc xboard.debug 1306493 8732196 47297515 xboard.debug
The problem I've had in the past (4.2.7) occurred mid-game where xboard thought the opponent was on move when it was in fact the player's move. This is the same thing that happened to Bob (and others) on FICS.sje wrote:I don't think that the time control has much to do with either bug, but I could be wrong. The bad-undo bug seems to be strongly linked to an out-of-turn opponent resignation; this may have a timing component, but not one related to the chess clock.mhull wrote:Bob (and others) had problems on FICS at CCT time controls. Maybe he could test his setup over there again with debug to see of the problem goes away.sje wrote:After 492 games, it's starting to look like activating the xboard debug output deactivates both the modify-after-free bug and the bad undo bug.hgm wrote:Hmm, let's hope not.Code: Select all
$ wc xboard.debug 1306493 8732196 47297515 xboard.debug
570 FICS games so far in a single session and no bugs yet with the debug flag activated. If you want to try your luck against my program at FICS, its handle is Symbolic and it's seeking blitz games.
"Abandon all hope, ye who enter debug mode."hgm wrote:Hmm, let's hope not.