[ntp:questions] refclock use causes core dump of ntpd

Harlan Stenn stenn at ntp.isc.org
Tue Feb 20 19:02:02 UTC 2007


> Program received signal SIGABRT, Aborted.
> 0x282aeecb in kill () from /lib/libc.so.6
> (gdb) where
> #0  0x282aeecb in kill () from /lib/libc.so.6
> #1  0x282aee68 in raise () from /lib/libc.so.6
> #2  0x282adb78 in abort () from /lib/libc.so.6
> #3  0x0807c87f in true_doevent (peer=0x80ad2b0, event=e_Poll) at refclock_true.c:788
> #4  0x0807cc53 in true_receive (rbufp=0x71ff) at refclock_true.c:540
> #5  0x08053046 in ntpdmain (argc=0, argv=0xbfbfeb50) at ntpd.c:1104
> #6  0x080532ff in main (argc=1, argv=0xbfbfec7c) at ntpd.c:317
> (gdb) exit

Well, the good news is the problem is now obvious.

We know it is from the call to abort() at line 788 of refclock_true.c.

Please open an issue a http://bugs.ntp.isc.org with this information.

The bad news is that refclock_true.c does not have a maintainer - anybody
want to volunteer?


More information about the questions mailing list