[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gnugo-devel] Re: GNUGo/kgsGtp Bug report
|
From: |
Gunnar Farnebäck |
|
Subject: |
Re: [gnugo-devel] Re: GNUGo/kgsGtp Bug report |
|
Date: |
Sun, 20 Mar 2005 23:52:21 +0100 |
|
User-agent: |
EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.3 Emacs/21.3 (sparc-sun-solaris2.9) MULE/5.0 (SAKAKI) |
Bill wrote:
> My understanding is that each undo undoes exactly one move. So, if black
> plays, then white, then the engine gets "undo", it should undo *only
> white's last move*.
That is correct.
> It looks like in this case kgsGtp sent an undo, and gnugo's next move
> was on top of the last stone *before* the un-done move.
>
> It is possible, though, that kgsGtp sent two undo's for some reason.
If that is at all possible I would suspect that's the case. GNU Go has
had no known undo problems since undo was reimplemented three years
ago. On the other hand it's very likely that it would regenerate the
same move if two undos were sent.
> Nick, please run in verbose mode (which prints all communication between
> kgsGtp and the engine), then if this happens again we'll know for sure
> where the bug is.
Indeed.
/Gunnar