From owner-freebsd-current Tue Aug 18 11:04:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00107 for freebsd-current-outgoing; Tue, 18 Aug 1998 11:04:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29981 for ; Tue, 18 Aug 1998 11:04:15 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id TAA00368; Tue, 18 Aug 1998 19:58:44 +0200 (CEST) To: Thomas Dean cc: current@FreeBSD.ORG Subject: Re: Calloc or VM Problem <== My Problem, Now Solved In-reply-to: Your message of "Tue, 18 Aug 1998 09:05:56 PDT." <199808181605.JAA14177@ix.netcom.com> Date: Tue, 18 Aug 1998 19:58:43 +0200 Message-ID: <366.903463123@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808181605.JAA14177@ix.netcom.com>, Thomas Dean writes: >Poul-Henning Kamp showed me how to find this >kind of problem. > > setenv MALLOC_OPTIONS UJA > ktrace -t u ./your-program > >It was my problem. You don't need the 'U' and the ktrace, unless you are making a tracefile, most malloc bugs seems to be caught with 'AJ'. I will recommend any software developer to ln -s AJ /etc/malloc.conf on their test machines. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message