Date: Thu, 19 Mar 1998 00:31:01 +0100 From: Eivind Eklund <eivind@yes.no> To: Greg Lehey <grog@lemis.com> Cc: FreeBSD current users <FreeBSD-current@FreeBSD.ORG> Subject: Re: Memory leak in inetd in last week's -current? Message-ID: <19980319003101.63504@follo.net> In-Reply-To: <19980319082033.12206@freebie.lemis.com>; from Greg Lehey on Thu, Mar 19, 1998 at 08:20:33AM %2B1030 References: <199803182125.NAA23054@dingo.cdrom.com> <587.890257623@critter.freebsd.dk> <19980319082033.12206@freebie.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980319003101.63504>