Date: Tue, 6 Jan 1998 11:56:49 +1030 From: Greg Lehey <grog@lemis.com> To: Jason Hudgins <jason@www.dancooks.com> Cc: jcj@phoenix.net, questions@FreeBSD.ORG Subject: Re: inetd coredumps repeatedly? Message-ID: <19980106115649.48897@lemis.com> In-Reply-To: <Pine.BSF.3.96.980105105827.15906A-100000@www.dancooks.com>; from Jason Hudgins on Mon, Jan 05, 1998 at 10:59:28AM -0600 References: <34B0B5DE.DD957ABE@basil.stthom.edu> <Pine.BSF.3.96.980105105827.15906A-100000@www.dancooks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 05, 1998 at 10:59:28AM -0600, Jason Hudgins wrote: >> Have youy examined the core dump, anything from the system logs? > > I've never examined a core dump before... =) Don't know how to > begin.. There's some information in the online handbook. To get much use out of it, you should recompile inetd with debugging symbols: # make clean all install clean CFLAGS=-g When you get the dump, start with something like: # gdb /usr/sbin/inetd inetd.core (gdb) dir /usr/src/usr.sbin/inetd (gdb) l (this will list where it died) (gdb) bt (this will show how it got there) > and unfortunatly the /var/log/messages just got turned over, its got a > total of two lines in it at the moment.. That's OK, the old /var/log/messages is now called /var/log/messages.0. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980106115649.48897>