From owner-freebsd-questions  Mon Jan 12 18:57:51 1998
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA17274
          for questions-outgoing; Mon, 12 Jan 1998 18:57:51 -0800 (PST)
          (envelope-from owner-freebsd-questions)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA17256
          for <freebsd-questions@FreeBSD.ORG>; Mon, 12 Jan 1998 18:57:44 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id SAA22188;
          Mon, 12 Jan 1998 18:57:25 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Date: Mon, 12 Jan 1998 18:57:25 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Guy Helmer <ghelmer@scl.ameslab.gov>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: inetd in realloc(): warning: junk pointer
In-Reply-To: <Pine.SGI.3.96.980106095609.10920A-100000@demios.scl.ameslab.gov>
Message-ID: <Pine.BSF.3.96.980112185627.22079R-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 6 Jan 1998, Guy Helmer wrote:

> A friend running 2.2.5 has run into the problem where inetd complains on
> incoming connections with "inetd in realloc: warning: junk pointer too low
> to make sense".  His system is a production telnet & mail server for his
> organization, and this message fouls up the protocols (ftp & pop
> especially), causing many problems.  inetd.c doesn't even call realloc(3),
> though, and there's only one unchecked memory allocation, a strdup(3) near
> the end of the source that doesn't look like it could be related to the
> problem.  /etc/inetd.conf is fine, as is /etc/services.
> 
> This problem has been mentioned many times before but I don't see whether
> anyone has resolved it.  Any solutions? 

None yet that I know of.  The biggest problem is that it's hard to
reproduce -- my machine doesn't give those errors.  If you can get a
consistent case and can attach gdb to it and give details, then we might
be able to do something with it.

Note that it could be a library call, if realloc() isn't called in the
program itself.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major