From owner-freebsd-current Wed Mar 18 15:31:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22840 for freebsd-current-outgoing; Wed, 18 Mar 1998 15:31:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22817 for ; Wed, 18 Mar 1998 15:31:04 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id XAA12955; Wed, 18 Mar 1998 23:31:02 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id AAA04476; Thu, 19 Mar 1998 00:31:02 +0100 (MET) Message-ID: <19980319003101.63504@follo.net> Date: Thu, 19 Mar 1998 00:31:01 +0100 From: Eivind Eklund To: Greg Lehey 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> <19980319082033.12206@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980319082033.12206@freebie.lemis.com>; from Greg Lehey on Thu, Mar 19, 1998 at 08:20:33AM +1030 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 19, 1998 at 08:20:33AM +1030, Greg Lehey wrote: > 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? Change free() to abort() instead of printing a message when it gets this error, and examine the coredump. Go from there. You can do this by % export MALLOC_OPTIONS=A before running inetd. % ln -s A /etc/malloc.conf will do the same for all programs. (If I understood the man-page correct, that is. Using the 'contents' of a symbolic link seems weird.) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message