Re: [Bug-gnubg] possible degrade with change set "protect movelist during autosave"

[Christian Anthon]

This was just a mistake in the bug fix. Reversed the source and the
destination in the movelist copy.

Christian.

2009/10/9 Jonathan Kinsey <address@hidden>:
> A safer approach is to only save in between move analysis, something like:
>
> main thread: wait until save timeout, then set flag (or event)
> worker threads: check flag before each move, if set increment a counter and
> wait
> for save to finish
> main thread: do save when all threads have stopped (then reset flag)
>
> This won't be great for performance if the save interval is small, but I
> assume
> analysis saving is only useful for very long match analysis operations.
>
> Jon
>
> 保坂範行 wrote:
>> Hi,
>>
>> How to reproduce:
>> Play a match with gnubg, then let gnubg to analyze match.
>> Do not get any move list for moves for the recorded match.
>>
>>
>> I'm very sure that this problem caused by change set "protect movelist
>> during autosave".
>> Built both source before change and source after change.
>>
>> I hope this report helps you.
>>
>> Nori
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Bug-gnubg mailing list
>> address@hidden
>> http://lists.gnu.org/mailman/listinfo/bug-gnubg
>
>
>
>
> ________________________________
> View your other email accounts from your Hotmail inbox. Add them now.
> _______________________________________________
> Bug-gnubg mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-gnubg
>
>