Re: [gnugo-devel] bug

[Arend Bayer]

Thanks a lot for your help, Tristan!

> error and it did not make an assertion failure, whereas it did so this
> morning. I am quite puzzled.
> 
> Is it possible that gnugo does not do the same things twice with the option -r
> 54 with the same gtpstream ?

No, unless there is some uninitialized memory access. I am now testing
for this with valgrind.

Btw, I tried to write you this before, but somehow the e-mail got
rejected on the way: if you 'ulimit -c 20000' before starting gnugo or
twogtp, you should get a core file. But since at least Dan seems to be
able to get a crash, we should be able to find this out ourselves now.

Arend