bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] GNU notes


From: Jim Segrave
Subject: Re: [Bug-gnubg] GNU notes
Date: Mon, 16 Sep 2002 20:23:17 +0200
User-agent: Mutt/1.4i

On Mon 16 Sep 2002 (13:46 -0400), Gary Wong wrote:
> On Sun, Sep 15, 2002 at 11:35:13PM -0300, Albert Silver wrote:
> > 1)                   So I'll start with the bug. I set up a position and
> > saved it, yet every single time I load it, it shows up with 17 (!)
> > pieces with an extra one on the bar and another taken off. If I enter
> > Edit and click on either piece they disappear, but it still shows when I
> > load it. I can zip this, but should I send it to this mailing list or
> > someone specific?
> 
> Thanks for the bug report.  I've made a patch now which should avoid
> problems when loading illegal positions, but I'm not sure how such a
> position would have been written in the first place.  If you are able
> to reliably reproduce .SGF files of illegal positions, please tell me
> how.

I'm wondering myself how it's done. The only way I've found to repeat
it is to take the original .sgf file and load it. Then if you manually
set up the correct position and save it, you get another .sgf file
which will have spectacularly wrong positions (I managed to hit 18
checkers at one point).
If you start gnubg from scratch and set up the position, everything
works.  Once a bad position has been imported, behaviour of gnubg
becomes unpredicatable.

Eg: 
start gnubg
set up the position HGccCEzZtgGCIQ and match QQnqAAAAAAAA. Save this
to an .sgf file. You can load this repeatedly without problems.
Now load the Snowie file that Albert posted. It will be patently
wrong. Set up the above position again and save it to a new .sgf
file. Now load your first .sgf file. It will appear to be wrong.

Exit gnubg and restart. Attempt to load the second saved .sfg file. It
will be wrong. Once a bad position has been loaded, any later saves
may be incorrect and any loading of files during the current run of
gnubg will be wrong.

The only question remaining is how to get that first incorrect file.

-- 
Jim Segrave           address@hidden




reply via email to

[Prev in Thread] Current Thread [Next in Thread]