I don't know that you will see it. This issue is not in current gnu glibc releases, at least none that we have including the most recent Fedora versions. But even worse, Mavericks gives you this when you run crafty and do the followingbnemias wrote:I do, at least from a library user's perspective-- I want to remove all such invalid assumptions from my code. But yeah, from a library maintainer's perspective, I would opt not to make changes solely for that reason.syzygy wrote:This type of "catching" bugs I do not consider a good reason.
Not that this is why the change was made. Bob asserts it was done for no good reason. Somehow, I'm unwilling to believe that until I see the actual changelog.
host% crafty
read pgnfile
Abort
host%
Does THAT seem like a reasonable thing to do? No hint as to what is wrong...
Here's an actual run with the bug, for fun...
scrappy% crafty
unable to open book file [./book.bin].
book is disabled
unable to open book file [./books.bin].
Crafty v23.6 (1 cpus)
White(1): read /users/hyatt/crafty/db.pgn
Abort
scrappy%
How's that for "being safe and helpful."
Reminds me of the 1970's era Xerox UTS operating system where if you typed any command incorrectly, it would simply say:
eh?
They eventually improved it to say
eh? (at 29)
where 29 was the character position where parsing broke down.
Giant step backward, IMHO. Which convinced several here to remove OS x and install Linux. I am now considering that myself since this is the second issue I have had (clang 1 year ago would not compile crafty correctly, every other version of gcc/icc/msvc/you-name-it compiled it perfectly. Looks like Apple is using Microsoft as a role model.