https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204048

--- Comment #1 from Jeremy Chadwick <[email protected]> ---
I can reproduce this problem on stable/9 using ports/net/ntp and
ports/net/ntp-devel too, though the stack trace looks different (maybe getting
clobbered, or maybe libevent takes care of something, not sure):

root@icarus:~ # pkg info | grep ntp
ntp-4.2.8p4                    The Network Time Protocol Distribution

root@icarus: # grep ntp /etc/rc.conf
# ntpd_flags: temporary workaround for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199127
ntpd_enable="yes"
ntpd_program="/usr/local/sbin/ntpd"
ntpd_config="/conf/ME/ntp.conf"
ntpd_sync_on_start="yes"
ntpd_flags="-4 -p /var/run/ntpd.pid -f /var/db/ntpd.drift"

root@icarus:~ # service ntpd start
Starting ntpd.
root@icarus:~ # dmesg -a | tail -1
pid 2425 (ntpd), uid 0: exited on signal 11 (core dumped)

root@icarus:~ # gdb /usr/local/sbin/ntpd /ntpd.core
...
#0  0x000000080134579d in _malloc_postfork () from /lib/libc.so.7
[New Thread 801807c00 (LWP 100886/ntpd)]
[New Thread 801807400 (LWP 100878/ntpd)]
(gdb) bt
#0  0x000000080134579d in _malloc_postfork () from /lib/libc.so.7
#1  0x0000000801347b3e in _malloc_postfork () from /lib/libc.so.7
#2  0x000000080134a3fe in _malloc_prefork () from /lib/libc.so.7
#3  0x000000080134c482 in calloc () from /lib/libc.so.7
#4  0x0000000801372ba6 in __res_state () from /lib/libc.so.7
#5  0x000000080137e98c in freeaddrinfo () from /lib/libc.so.7
#6  0x00000008013a361a in nsdispatch () from /lib/libc.so.7
#7  0x000000080137fffb in getaddrinfo () from /lib/libc.so.7
#8  0x0000000000461c3d in ?? ()
#9  0x0000000000462293 in ?? ()
#10 0x00000000004648c9 in ?? ()
#11 0x00000008010a6e70 in pthread_getprio () from /lib/libthr.so.3
#12 0x0000000000000000 in ?? ()

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[email protected]"

Reply via email to