Re: [gnugo-devel] improving bug reports

[aquarius]

Hi,

just an addition to your really useful proposal:

Why not include the random seed and level in the SGF
 - just as the ascii mode save command does?
This way nobody would accidently omit this information when cutting the
debug output since the random seed is only in the last two lines now
and level is never shown by now.

Or go one step further and make the header of the SGF look exactly
like the one of the save command ... ? Or even include the whole
assertion failure and showboard output inside a GC node in the SGF ... ?
So one could save the whole bunch as an sgf file.

N.B. the latter would of cause only work if dump_board_sgf will never fail.

N.B. I'm sure you mean "intended" rather than "This is only attended as a
     stand-alone debug tool" in the introducing comment of dump_board_sgf.

happy go - ing
   aquarius

Gunnar Farnebäck wrote:

> I wrote:
> > The patch below removes all board output except at the top of the
> > stack and writes an sgf of the game up to the bottom of the stack.
>
> A sample assertion failure (artificially provoked) may look like this
> after the patch:
...
> (;GM[1]FF[4]SZ[19]KM[0.5]GN[GNU Go 3.5.8 stepped on a bug]
...
> )
> gnugo 3.5.8 (seed 1086724294): You stepped on a bug.
> Please mail this message, including the debug output above, to address@hidden
>
> /Gunnar