Date: Wed, 24 Mar 1999 22:28:57 -0500 From: "Matt White" <mwhite@donet.com> To: "Frederic LOYER" <loyer@ensta.fr> Cc: <freebsd-stable@FreeBSD.ORG> Subject: RE: Strange Error Message Message-ID: <000401be766f$9e0f41c0$0402030a@yiff.bunnynet.org> In-Reply-To: <199903221904.UAA20478@quickstep.ensta.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
It hasn't happened again, so I can't reproduce it either. The same box has now been up since that incident without any problems... Oh well. =) Matt -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Frederic LOYER Sent: Monday, March 22, 1999 2:04 PM To: Matt White Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Strange Error Message > Hello... > > Today while copying a large number of files I started getting this error > message: > > inetd in realloc(): warning: junk pointer, too low to make sense. > inetd in free(): warning: junk pointer, too low to make sense. > > This is a -STABLE system, last cvsupped and built on the 20th of this month. > > Any idea what this means? It prevented me from logging in, whenever I'd try > to start up a telnet session it would toss those two lines to me and close > the session. (I was still able to ssh in, which is not started via inetd.) > > Thanks, > Matt I've found the same problem. This means there is a bug in "inetd" or one of the called libraries. Trying to work with a debugger is difficult since inetd crash after the fork(): you can't login but the "main" inetd process is still alive to answer the following connection... and crash again. It seems to happen in malloc() called from login_getclass()... but this doesn't tell us where the memory is screwed: there must be something wrong before the fork() since this error comes on *every* connection after the first error. It could be triggered by the folowing lines: comsat dgram udp wait tty:tty /usr/libexec/comsat comsat ntalk dgram udp wait tty:tty /usr/libexec/ntalkd ntalkd tty:tty is quite recent on -STABLE, and I don't remember seeing this error before updating /etc/inetd.conf. Anyway this error is too rare to be debugged easily (I can't reproduce it). -- Frederic Loyer <loyer@ensta.fr> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000401be766f$9e0f41c0$0402030a>