On Mon, Feb 20, 2012 at 01:52, Mark C. Stephens <[email protected]> wrote: > Also with –D2 there are, for what it looks like to me, garbage chars on the > debug output: > > refclock_gtlin: fd 5 time 3538687955.517997 timecode 0 > ╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠ > ╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠╠░ì└ > refclock_gtlin: fd 5 time 3538687956.008909 timecode 71 > $GPGGA,005237,3345.9174,S,15105.4586,E, > 0.5,M,,
The invalid characters are from a bug in the debug trace output of refclock_gtlin introduced in 4.2.7p257 with the fix for bug 2135. The word 'timecode' is followed by the current length of the timecode, then its contents. As of p257 when the length is 0, the timecode buffer is not zero-terminated. p259 should have the fix to suppress the timecode buffer display when it's logically empty. Thanks for the report, Dave Hart _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
