Author: Robert Hyatt
Date: 09:51:21 02/05/03
Go up one level in this thread
On February 04, 2003 at 23:28:52, Mike Byrne wrote:
>On February 04, 2003 at 23:11:45, Robert Hyatt wrote:
>
>>On February 04, 2003 at 22:44:59, Mike Byrne wrote:
>>
>>>On February 04, 2003 at 17:01:28, Robert Hyatt wrote:
>>>
>>>>On February 04, 2003 at 14:38:31, Joshua Haglund wrote:
>>>>
>>>>>How come Crafty 19.12 crashes with winboard if it has a book with a different
>>>>>version of Crafty?
>>>>>
>>>>>It didn't do that before. I just didn't use the .bin files
>>>>>
>>>>>Any clues,
>>>>>
>>>>>Joshua
>>>>
>>>>Do you mean 19.2???
>>>>
>>>>It shouldn't crash, as the book format has not changed for a couple of years
>>>>now. If it
>>>>is crashing, that is unexpected behavior...
>>>
>>>Bob,
>>>
>>>this is the code that triggers it --
>>>"
>>> if (major<17 || (major==17 && minor<0)) {
>>> Print(4095,"\nERROR! book.bin not made by version 17.0 or later\n");
>>> fclose(book_file);
>>> fclose(books_file);
>>> book_file=0;
>>> books_file=0;
>>> }
>>>"
>>>
>>>if I comment this out - everything works. I do not create a new book very
>>>often, but I was just experimenting with a new book and I came accross the same
>>>problem. Something has change with the "version" check - but I am not sure
>>>what. I'm also not sure if it is strictly related to MSVC++ complies or all.
>>>If I use the book I had have for a while - it works. But I cannot create a new
>>>book that works unless I "comment out" this version check.
>>
>>
>>I'll look again. But I have created books within the last two weeks that
>>worked fine. In fact, I created one for the last CCT event.
>>
>>However, that should _not_ make it "crash". Crafty simply won't use the
>>book. the original post suggested it was actually crashing and dumping
>>core, which seems strange...
>
>for the pocket pc crafty -- it crashes ...for the pc crafty, it simply does not
>use the book on my machine -- in winboard that could look like crash - since he
>may be waiting a few minutes for a move (depending on this tc) and he might have
>thought it crash ...but you're right - it doesn't crash on my machine
If it crashes, it means that there is something wrong in the PPC port. IE
book_file is
normally an open file descriptor unless the book is considered useless. In that
case,
it is set to zero (0) and the various book reads and writes are "protected" by
testing
for zero before using the descriptor. If one of those checks was removed, it
would
definitely crash as you can't pass a zero file pointer to read() or write()...
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.