bug-gnubg
[Top][All Lists]
Advanced

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

Re: Fw: [Bug-gnubg] Latest GnuBG Win distrib available at www.gnubg.org


From: Christian Anthon
Subject: Re: Fw: [Bug-gnubg] Latest GnuBG Win distrib available at www.gnubg.org
Date: Thu, 21 Feb 2008 00:09:11 +0100

Found the mistake. If #define's weren't so useful at times, I think
they should be abolished.

Christian.

On Wed, Feb 20, 2008 at 5:47 PM, Massimiliano Maini
<address@hidden> wrote:
>
> >A few extra details that may help: in the nogui version, loading an
> analyzed match and trying to add it:
> >
> >(Game over) relational add match
> >close, 0 0
> >Traceback (most recent call last):
> >  File "<string>", line 1, in <module>
> >  File "database.py", line 101, in PyUpdateCommand
> >    cursor.execute(stmt)
> >sqlite3.OperationalError: 77 values for 76 columns
> >(Game over)
>
> In the console (GUI version) I see:
>
> Traceback (most recent call last):
>   File "<string>", line 1, in <module>
>   File "database.py", line 101, in PyUpdateCommand
>     cursor.execute(stmt)
> sqlite3.OperationalError: 77 values for 76 columns
>
> (gnubg-gui-py-sse-wmt-debug.exe:1548): Pango-WARNING **: Invalid UTF-8
> string pa
> ssed to pango_layout_set_text()
>
> Is it a double bug ?
> One is the problem in AddStats reported by Jon, the other (possibly) an
> error message wrongly displayed ?
>
>
> Concerning the problem found by Jon:
>
> >Looks like it's this line:
>  >                 g_print("close, %d %d\n", player,
> sc->anCloseCube[player]);
>  >in AddStats(), I assume it should be:
>  >                 APPENDI("close", sc->anCloseCube[player]);
>  >
>  >Or maybe something slightly different?
>
> I think you simply have to remove the line:
>
>         g_print("close, %d %d\n", player, sc->anCloseCube[player]);
>
> Doing this, it works for me on a 3pt match.
>
> On the other hand, I have another match (1pt) that makes it crash even after
> the removal
> of the above line. One thing I have noticed is that this match ends with a
> resign.
> The resign is correct (and the accept is correct too), but in the analysi it
> is flagged as
> very bad 9and the accept too). Maybe there's something strange there ...
> I'll send you the sgf file separately.
>
> MaX.
>




reply via email to

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