Upgrading to clock.c version 1.84 seems to make everything happy.. (that
might not be what fixed it, but I didn't notice anything else change..)

On Sun, Jul 04, 2004 at 01:11:48PM +0100, Patrick Welche wrote:
> Anyone else seeing this? 3 Jul -current, i386 running ntpq:
> 
> # ntpd -d -d -d
> ntpd 4.2.0-r Sat Jul  3 19:47:24 BST 2004 (1)
> addto_syslog: ntpd 4.2.0-r Sat Jul  3 19:47:24 BST 2004 (1)
> addto_syslog: set_process_priority: Leave priority alone: priority_done is <2>
> addto_syslog: precision = 2.000 usec
> create_sockets(123)
> address_okay: listen Virtual: 1, IF name: ex0, Up Flag: 1
> address_okay: listen Virtual: 1, IF name: ex0, Up Flag: 1
> address_okay: listen Virtual: 1, IF name: ex0, Up Flag: 1
> address_okay: listen Virtual: 1, IF name: lo0, Up Flag: 1
> address_okay: listen Virtual: 1, IF name: lo0, Up Flag: 1
> address_okay: listen Virtual: 1, IF name: lo0, Up Flag: 1
> bind() fd 4, family 2, port 123, addr 0.0.0.0, flags=8
> ...
> interface 7:  fd=11,  bfd=-1,  name=lo0,  flags=0x5
>               sin=fe80::1  mask=ffff:ffff:ffff:ffff::
> init_io: maxactivefd 11
> local_clock: time 0 offset 0.000000 state 0
> addto_syslog: frequency initialized 20.180 PPM from /var/db/ntp.drift
> local_clock: time 0 offset 0.000000 state 1
> Segmentation fault (core dumped)
> 
> Program terminated with signal 11, Segmentation fault.
> 
> (gdb) bt
> #0  0x480a680e in _rtld_bind () from /usr/libexec/ld.elf_so
> Cannot access memory at address 0xbfbec000
> 
> ?!
> 
> Cheers,
> 
> Patrick