I hate finding core files from system daemons.  I really hate it when
those daemons are listening for network connections.  I really really
really hate it when those daemons are running as root!  The only thing
worse could be finding an inetd.core....

This traceback is from a mostly stock NetBSD/i386-1.3.3 system (so far
as I can tell there have been no local changes in any of the code path
reported below):

14:29 [2018] # gdb /usr/sbin/inetd /inetd.core 
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.16 (i386-netbsd), Copyright 1996 Free Software Foundation, Inc...
(no debugging symbols found)...
Core was generated by `inetd'.
Program terminated with signal 10, Bus error.
Reading symbols from /usr/libexec/ld.so...(no debugging symbols found)...done.
Reading symbols from /usr/lib/libwrap.so.0.0...(no debugging symbols found)...
done.
Reading symbols from /usr/lib/libc.so.12.20...(no debugging symbols found)...
done.
#0  0x4005bf78 in dn_expand ()
(gdb) where
#0  0x4005bf78 in dn_expand ()
#1  0x40037134 in __getnetbyaddr ()
#2  0x40037b7f in gethostbyaddr ()
#3  0x4001e2a7 in sock_hostname ()
#4  0x4001ea3a in eval_hostname ()
#5  0x4001ea5f in eval_hostinfo ()
#6  0x4001eac1 in eval_client ()
#7  0x2161 in run_service ()
#8  0x1ef5 in main ()
(gdb) quit

Unfortunately without debugging symbols I can't easily tell if it was
about to reject a connection, or was just logging it, or indeed what was
in the "req" structure that had been handed to eval_client()....

I've still got a copy of the core file should anyone have any
suggestions to find more details.

-- 
							Greg A. Woods

+1 416 218-0098      VE3TCP      <gwoods@acm.org>      <robohack!woods>
Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>