[gnugo-devel] matcher_status question

[Evan Berggren Daniel]

OK, so I think I've almost got the matcher_status state change checker
done, but there's a couple things weird.

First, I think the result of the discussion about my matcher_status patch
was that, as implemented, it would only ever return states of ALIVE, DEAD
or CRITICAL, and never UNKNOWN.  however, I am getting all four.  Is this
a big with my code, or is something else going wrong?  it's fairly
repeatable -- just load up an early stage small game, and it'll show
UNKNOWNs.

Second, for some unknown reason GNU Go isn't finishing it's games, I don't
think.  the sgf file attached is an example of such.  Any idea what's
going on?

Thanks

Evan Daniel

(;GM[1]FF[4]RU[Japanese]SZ[9]HA[0]KM[5.5];B[gc]
;W[dc]
;B[gf]
;W[dg]
;B[ce]
;W[tt]
;B[bc]
;W[cc]
;B[bb]
;W[fb]
;B[bg]
;W[de]
;B[gb]
;W[cf]
;B[be]
;W[fc]
;B[fa]
;W[bf]
;B[af]
;W[cb]
;B[ba]
;W[ca]
;B[ef]
;W[cg]
;B[bh]
;W[eg]
;B[cd]
;W[ee]
;B[fg]
;W[dd]
;B[ff]
;W[df]
;B[fh]
;W[ea]
;B[ga]
;W[tt]
;B[tt]
)