Re: [gnugo-devel] minor bug on owl.c

[Gunnar Farnebäck]

Emanuele Cisbani wrote:
> The GTP command causing the abend is:
> analyze_semeai B3 C4
>
> It's not correct, ok, but we can expect a less tragic reply then this:
>
> ***assertion failure:
> owl.c:503 - board[apos] == OTHER_COLOR(board[bpos]) near B3***
>
>
>    A B C D E F G H J K L M N O P Q R S T
> 19 . . . . . . . . . . . . . . . . . . . 19
> 18 . . . . . . . . . . . . . . . . . . . 18
> 17 . . . . . . . . . . . . . . . . . . . 17
> 16 . . . + . . . . . + . . . . . + . . . 16
> 15 . . . . . . . . . . . . . . . . . . . 15
> 14 . . . . . . . . . . . . . . . . . . . 14
> 13 . . . . . . . . . . . . . . . . . . . 13
> 12 . . . . . . . . . . . . . . . . . . . 12
> 11 . . . . . . . . . . . . . . . . . . . 11     WHITE (O) has 
captured 0 stones
> 10 . . . + . . . . . + . . . . . + . . . 10     BLACK (X) has 
captured 0 stones
>  9 . . . . . . . . . . . . . . . . . . . 9
>  8 X X X X . . . . . . . . . . . . . . . 8
>  7 O O O X . . . . . . . . . . . . . . . 7
>  6 . . O X . . . . . . . . . . . . . . . 6
>  5 X O O X . . . . . . . . . . . . . . . 5
>  4 . X O X . . . . . + . . . . . + . . . 4
>  3 X O . X . . . . . . . . . . . . . . . 3
>  2 . O . X . . . . . . . . . . . . . . . 2
>  1 O O X . . . . . . . . . . . . . . . . 1
>    A B C D E F G H J K L M N O P Q R S T
> (;GM[1]FF[4]SZ[19]KM[6.5]HA[0]GN[GNU Go 3.7.11 stepped on a bug]
> ;B[aq];B[ao];B[al];B[bp];B[bl];B[cs];B[cl];B[dr];B[dq];B[dp];B[do];B[dn]
> ;B[dm];B[dl];W[as];W[am];W[bs];W[br];W[bq];W[bo];W[bm];W[cp];W[co];W[cn]
> ;W[cm]
> )
> gnugo 3.7.11 (seed 1978642549): You stepped on a bug.
> Please mail this message, including the debug output above, to 
address@hidden

This is the normal response if you make a serious mistake when
modifying the code in GNU Go. Obviously it's designed for trapping the
difficult to find bugs that remain in stable releases, but I think
it's fine for developers too.

It can be discussed whether GTP mistakes should be handled more
gracefully. The official commands from the GTP spec are handled
gracefully but for other commands of internal testing and debugging
character we haven't spent time and code lines on doing sanity checks
needed for graceful failures. I'm doubtful that we should either.

> This application has requested the Runtime to terminate it in an 
unusual way.
> Please contact the application's support team for more information.

This has been added by your OS or some other part of your environment.
It seems a bit over-ambitious for a simple EXIT_FAILURE exit code.

/Gunnar