From owner-freebsd-questions Thu Jul 27 11:14:16 2000 Delivered-To: freebsd-questions@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 9C8CA37B68A for ; Thu, 27 Jul 2000 11:14:04 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 13Hqmi-00099E-00; Thu, 27 Jul 2000 17:45:24 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 13Hqmi-000NTA-00; Thu, 27 Jul 2000 17:45:24 +0100 Date: Thu, 27 Jul 2000 17:45:24 +0100 From: Ben Smithurst To: Ben Williams Cc: freebsd-questions@FreeBSD.ORG Subject: Re: junk pointer in realloc() ? Message-ID: <20000727174524.E59315@strontium.scientia.demon.co.uk> References: <1538517957.20000727011508@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <1538517957.20000727011508@home.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Williams wrote: > I ran across something a little odd this evening when telnet'ing to my > "venerable" (2.2.5-RELEASE) system. > > --------------------terminal copy-n-paste-------------------- > $ telnet core > Trying 208.150.25.3... > Connected to core.instantemail.net. > Escape character is '^]'. > inetd in realloc(): warning: junk pointer, too low to make sense. > --------------------terminal copy-n-paste-------------------- > > What does this inetd line mean? It means someone did realloc(some_pointer, some_size) in inetd and some_pointer wasn't a valid pointer. That's basically rephrasing the error message, so I might not be being too helpful here. :-) I'll I can suggest is you upgrade that machine at least to 2.2-STABLE if you don't want a more major upgrade than that. If you don't even want to do that, you could check out src/usr.sbin/inetd from RELENG_2_2 and just rebuild inetd. That still might not fix it, I think some more bugs like this in inetd have been fixed since RELENG_2_2, and using a more recent inetd probably wouldn't work on RELENG_2_2. (You could try it though, at your own risk. I'd pick the RELENG_3 inetd so you don't get IPv6 stuff involved anywhere.) The other fix is to use ssh instead of telnet. ;-) -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D FreeBSD Documentation Project / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message