From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: * X-Spam-Status: No, score=1.4 required=5.0 tests=SPF_NEUTRAL autolearn=disabled version=3.1.3 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id B7B5CBC69 for ; Mon, 12 Nov 2007 21:53:29 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAIdLOEdIDszhh2dsb2JhbACPCgEBAQgEBBMRgRY X-IronPort-AV: E=Sophos;i="4.21,406,1188770400"; d="scan'208";a="19202204" Received: from qb-out-0506.google.com ([72.14.204.225]) by mail4-smtp-sop.national.inria.fr with ESMTP; 12 Nov 2007 21:53:29 +0100 Received: by qb-out-0506.google.com with SMTP id e11so2592745qbe for ; Mon, 12 Nov 2007 12:53:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=OXB4Ru/6bd1ti3+Qg9UKiJkGsZp0zfY+p5rwKQUJF8Q=; b=UUtJdLQ3pn/I4LrZENn5HT1DZWSh4goQxK/yUR80SLgT1SjBM3+eGk23qWas0TRs/qzm6KzfDgsxsoctmkdloV5SDZdz22dNm7U/8gL/aX3XHgoEXs85gLH12X7ipjcOT2zOu7jOP1bPBs+Z2h+yLcYvABMU92xSvkFFGqR+GgM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=pZV+s1uV+xucPvwHNgqLq/BcUHncs7oPM6JV3dmGakaYiDVtUOY1E4VLs4DaAPyVD85oom2vAIy2+8VVQRB5KkITNGnKBhhpRWIEECUFnWFS/0ubT3wRkSVEB9f3c1wY/HJUOZa6RXLTv4T+Thjfg/w0GjOCT33npUPyWQuD0IA= Received: by 10.142.126.17 with SMTP id y17mr1161256wfc.1194900806902; Mon, 12 Nov 2007 12:53:26 -0800 (PST) Received: by 10.64.21.4 with HTTP; Mon, 12 Nov 2007 12:53:26 -0800 (PST) Message-ID: <1f4f725e0711121253y2b63cb2ag94af4f0c8642285a@mail.gmail.com> Date: Mon, 12 Nov 2007 21:53:26 +0100 From: "Fabrice Le Fessant" Sender: fabrissimo@gmail.com To: "=?ISO-8859-1?Q?Pierre_Etchema=EFt=E9?=" Subject: Re: [Caml-list] debugging memory leaks Cc: caml-list@yquem.inria.fr In-Reply-To: <20071112085325.01abdcf3.petchema@concept-micro.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <86183D4E-184A-4F26-84F9-93411D070B38@maubi.net> <20071112085325.01abdcf3.petchema@concept-micro.com> X-Google-Sender-Auth: 88f2da6e5abac6c7 X-Spam: no; 0.00; ocaml-:01 author's:01 saclay:01 ocaml:01 minimally:01 compiler:01 ocaml:01 ocaml-:01 beginner's:01 bug:01 beginners:01 wrote:01 maintainer:01 heap:01 pps:01 Interesting, I did a patch in 2004, called ocaml-memprof for ocaml-3.07,but there is not a single reference/credit to it on this page... Given the inheritance, the maintainer should be careful to keep the original author's name. - Fabrice Le Fesasnt ASAP Project, INRIA Saclay On Nov 12, 2007 8:53 AM, Pierre Etchema=EFt=E9 = wrote: > Le Sun, 11 Nov 2007 21:56:06 -0800, Chris Waterson a= =E9crit : > > > I have a fairly substantial OCaml application that leaks memory. > > What tools or techniques do people use to track down memory leaks? > > Minimally, is there a way to enumerate the live objects in the heap? > > There's ocaml-memprof, a compiler patch that adds memory profiling > features to ocaml programs; > > Latest update of the patch itself, as far as I know: > http://www.pps.jussieu.fr/~smimram/docs/ocaml-3.09.3-memprof.patch > > Readme: > http://www.pps.jussieu.fr/~smimram/docs/README.memprof > > > _______________________________________________ > Caml-list mailing list. Subscription management: > http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list > Archives: http://caml.inria.fr > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs >