From owner-freebsd-current Sat Mar 25 12:31:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id CEB8D37B929 for ; Sat, 25 Mar 2000 12:31:39 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id VAA00929; Sat, 25 Mar 2000 21:31:34 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Arun Sharma Cc: FreeBSD Current Subject: Re: malloc.conf In-reply-to: Your message of "Sat, 25 Mar 2000 12:29:02 PST." <20000325122902.A10626@sharmas.dhs.org> Date: Sat, 25 Mar 2000 21:31:34 +0100 Message-ID: <927.954016294@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000325122902.A10626@sharmas.dhs.org>, Arun Sharma writes: >On Sat, Mar 25, 2000 at 09:05:18PM +0100, Poul-Henning Kamp wrote: >> In message <20000325120159.A10568@sharmas.dhs.org>, Arun Sharma writes: >> >On Sat, Mar 25, 2000 at 08:55:16PM +0100, Poul-Henning Kamp wrote: >> >> >> >> Please read the malloc(3) manual page. >> >> >> > >> >I did and created malloc.conf as documented there. And things were >> >fine after that. Wouldn't it be better if the build process created >> >a default /etc/malloc.conf ? >> >> Exactly how did you create it ? > >Just as it is documented: > >ln -s 'A<' /etc/malloc.conf And that made your program not dump core ? In that case you should rather try: ln -sf 'AJ' /etc/malloc.conf and fix the bug in your program. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message