Date: Fri, 23 Oct 1998 19:49:25 -0500 From: "Brian C. Grayson" <bgrayson@marvin.ece.utexas.edu> To: Doug White <dwhite@resnet.uoregon.edu>, Philippe Regnauld <regnauld@deepo.prosa.dk> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: inetd in realloc(): ... && 2.2.6 Message-ID: <19981023194925.A10335@marvin.ece.utexas.edu> In-Reply-To: <Pine.BSF.4.03.9810121355350.25080-100000@resnet.uoregon.edu>; from Doug White on Mon, Oct 12, 1998 at 01:56:25PM -0700 References: <19981012191137.41278@deepo.prosa.dk> <Pine.BSF.4.03.9810121355350.25080-100000@resnet.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 12, 1998 at 01:56:25PM -0700, Doug White wrote: > On Mon, 12 Oct 1998, Philippe Regnauld wrote: > > > I'm seeing this: > > > > regnauld@deepo % ftp localhost > > Connected to localhost. > > inetd in realloc(): warning: junk pointer, too high to make sense. > > > > This is a 2.2.6-RELEASE box. > > This is a known bug, as you appear to know... ... > Yes, it's very, very hard to track. If you cn get it to pop up > predictably, set up malloc(3) to cause a core dump and backtrace the > resulting core. I just got bitten by this also. It prevented logins, as rlogin would die as soon as it saw a non-NULL first character. :( And ssh is apparently hosed, and we don't use telnet (too insecure!). Unfortunately, I killed and restarted inetd before I saw the above. Interestingly, sshd appears to have gotten hosed at the same time: Oct 23 19:31:15 sim1 sshd[8903]: fatal: xmalloc: out of memory (allocating 1073688827 bytes) Could this be related, or just pure coincidence? I'll keep that sshd running for a while... This is all in 3.0-19980804-SNAP, BTW. Brian -- "...and the particle undergoes a BOINNNNG..." - Dr. Dunning, PHYS 202 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981023194925.A10335>