Re: [gnugo-devel] Bug report gnugo-3.3.8

[Arend Bayer]

Hi Markus,

> I initialize GnuGo with:
>
> gg_srand(0); /* Undocumented in the GnuGo docs but necessary */
I think you should instead set the global variable random_seed.

> init_gnugo(32);
> level = 0;

>
> The assertion output is:
>
> ***assertion failure:
> move_reasons.c:431 - k < 100 near PASS***
>
>
>    A B C D E F G H J
>  9 . . . . . . O . . 9
>  8 . . . . . . . X . 8
>  7 . . + . . . + . . 7
>  6 . . . . . . . . . 6
>  5 . . . . + . . . . 5
>  4 . . . . . . . . . 4
>  3 . . + . . . + . . 3
>  2 . . . . . . . . . 2     WHITE has captured 0 stones
>  1 . . . . . . . . . 1     BLACK has captured 0 stones
>    A B C D E F G H J
>
> gnugo 3.3.8 (seed 0): You stepped on a bug.
>
> The debugger shows that k==100, is this bug related to the FIXME comment
> following in move_reason.c:add_move_reason() or am I doing something wrong
> with initializing or using the GnuGo API?

Are you calling reset_engine()? You have to do so after every change to
the board position before you call examine_position. gg_srand also gets
called automatically from there.

The docs about the GNU Go API may be somewhat out of date, I haven't
looked at them recently.

Arend