WZZZ wrote:
Re. the "edge case" crash scenario we have been discussing, someone elsewhere wrote :
Keep in mind that gcc normally produces executables that are optimized for the system it's being compiled on. As a result the edge cases could be a particular CPU that doesn't implement a particular instruction that flatsixracer's CPU does implement.
Wonder what you think of that?
Except that like you, I build my own ntp files on my own system (I have Xcode 3.2.6) so that argument doesn't apply for me either. Of course that doesn't mean that the gcc compiler itself doesn't have a code generation bug (it does compile the code with -O2 optimization level enabled) but I really really don't believe that :-)
Also, by the way, the crash report you showed earlier, which I said was the same as mine, was not an ILLEGAL INSTRUCTION report. It appears to be for a pointer attempting to use a chunk of freed memory. That's what lead me to believe it was a rare edge condition. Some condition drove it down a path where it freed a pointer but some other place thought the pointer was still valid, or maybe it attempted to free the same pointer twice. That makes it a coding bug in my book! And unless the code authors know their code really well (you would hope), and/or this happens more often to others, and the edge condition can be fully understood, errors of this kind can be a b*tch for fix.
And by the way, I used the instructions at MI to do the 4.2.8 update (compiling from Xcode 3.2) on one of my clones. Don't see the sntp -v error and I am seeing there what appears to be the ntp-restrict.conf as well. The explanation might be that, perhaps, it didn't fully overwrite flatsixracers' rev 4, which I had first installed, but no idea why that would have happened, nor does it seem likely, since I took it all the way.
I believe I asked you about that earlier in this thread (i.e., where was the -v error report in your system.log?). It would be (have been) easy to check, i.e., just look at the sntp command line in the /usr/libexit/ntpd-wrapper file. You must have the updated one with the sntp -K ... fix.