Re: [Bug-gnubg] Latest Win build issues

[motiv4u]

This build does not show the #Q0 issue anymore (even with the cache
activated). I was one of the few(?) having that challenge with your
build. So far so good.

It does however reintroduce the automatic new match. Start a match,
first occasion resign backgammon (gnubg accepts). Continue next game.
Go back to the previous game, go forward to the new game, click in the
dice area: gnubg starts a new 7 pointer (my default).

N.

On Tue, Feb 3, 2009 at 11:25 AM, Massimiliano Maini
<address@hidden> wrote:
>
> Hi all,
>
> from what I've seen, it seems that Jon's workaround for the #Q0 issue,
> garbage in rollout output
> (add the code "((cacheNode*)e)->ar[5] = ((cacheNode*)e)->ar[6] = 0;" at the
> beginning of the
> CacheAdd() function in cache.c) has broken things even more.
> Jon said the extra line solved the #Q0 issue, but it has introduced the new
> one (wrong values in
> the MWC and equities at different plies): one the extra line of code
> removed, I no longer see
> strange MWC.
>
> This explains why the "new" bug was only in my builds (I was the only one
> with the extra line of
> code).
>
> I have rebuilt everything and put the new distrib (GTK has been updated too,
> so reinstall everything)
> on gnubg.org. Most likely, we will face again the #Q0 bug in rollout output.
>
> MaX.
> _______________________________________________
> Bug-gnubg mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-gnubg
>
>



-- 
"He is no fool who gives up what he cannot keep to gain what he cannot
lose." -Jim Elliot