From owner-freebsd-current Wed Mar 18 13:50:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00972 for freebsd-current-outgoing; Wed, 18 Mar 1998 13:50:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00941 for ; Wed, 18 Mar 1998 13:50:39 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id IAA11128; Thu, 19 Mar 1998 08:20:34 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id IAA12474; Thu, 19 Mar 1998 08:20:33 +1030 (CST) (envelope-from grog) Message-ID: <19980319082033.12206@freebie.lemis.com> Date: Thu, 19 Mar 1998 08:20:33 +1030 From: Greg Lehey To: Poul-Henning Kamp , Mike Smith Cc: FreeBSD current users Subject: Re: Memory leak in inetd in last week's -current? References: <199803182125.NAA23054@dingo.cdrom.com> <587.890257623@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <587.890257623@critter.freebsd.dk>; from Poul-Henning Kamp on Wed, Mar 18, 1998 at 10:47:03PM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 March 1998 at 22:47:03 +0100, Poul-Henning Kamp wrote: > In message <199803182125.NAA23054@dingo.cdrom.com>, Mike Smith writes: >>> I've just discovered that my inetd has been rejecting connections with >>> the following message: >>> >>> $ ftp ftp.lemis.com >>> Connected to freebie.lemis.com. >>> inetd in realloc(): warning: junk pointer, too high to make sense. >>> ftp> >>> >>> I took a ktrace of it happening, if that's of any use, and restarted >>> inetd, which made the problem go away. Any ideas? >> >> Bug in inetd, normally associated with malloc failure (system out of >> memory). >> >> Possibly bad use of a low (nonzero) magic pointer value, or possibly >> attempting to use a pointer to a static item as a substitute. > > Wrong. > > It says "too >high< to make sense". > > Likely causes: > > pointer to a stack item > pointer to a previously free'ed piece of memory. > pointer to mmaped memory, for instance shlib data > uninitialized pointer. > > Technically it means that the pointer is higher than sbrk(0). Now *that*'s the kind of information which makes sense to me. OK, that looks like a program logic bug, not the results of loss of swap space (of which I should have always had at least 80 MB over). Any ideas about how to look for this particular needle in a haystack? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message