From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <yallop@gmail.com>
X-Original-To: caml-list@sympa.inria.fr
Delivered-To: caml-list@sympa.inria.fr
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83])
	by sympa.inria.fr (Postfix) with ESMTPS id A7B6A7F986
	for <caml-list@sympa.inria.fr>; Fri, 27 Jun 2014 16:33:04 +0200 (CEST)
Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender
  authenticity information available from domain of
  yallop@gmail.com) identity=pra; client-ip=74.125.82.180;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="yallop@gmail.com";
  x-sender="yallop@gmail.com"; x-conformance=sidf_compatible
Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of
  yallop@gmail.com designates 74.125.82.180 as permitted
  sender) identity=mailfrom; client-ip=74.125.82.180;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="yallop@gmail.com";
  x-sender="yallop@gmail.com"; x-conformance=sidf_compatible;
  x-record-type="v=spf1"
Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@mail-we0-f180.google.com) identity=helo;
  client-ip=74.125.82.180;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="yallop@gmail.com";
  x-sender="postmaster@mail-we0-f180.google.com";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnUBAGeArVNKfVK0m2dsb2JhbABAGoNfWoJup1UGmXABgQAIFg8BAQEBAQYLCwkUKIQDAQEBBBIRHQEbHQEDDAYFCw0CAiYCAiEBAREBBQEcGSKICwEDEQ02mWxqiyeBcoMQkQsKGScNZIVsEQEFDYEehDmGe4ImBxaCYYFMBZhfgX6BRowlhB8YKYRzPC8
X-IPAS-Result: AnUBAGeArVNKfVK0m2dsb2JhbABAGoNfWoJup1UGmXABgQAIFg8BAQEBAQYLCwkUKIQDAQEBBBIRHQEbHQEDDAYFCw0CAiYCAiEBAREBBQEcGSKICwEDEQ02mWxqiyeBcoMQkQsKGScNZIVsEQEFDYEehDmGe4ImBxaCYYFMBZhfgX6BRowlhB8YKYRzPC8
X-IronPort-AV: E=Sophos;i="5.01,560,1400018400"; 
   d="scan'208";a="82542379"
Received: from mail-we0-f180.google.com ([74.125.82.180])
  by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 27 Jun 2014 16:32:45 +0200
Received: by mail-we0-f180.google.com with SMTP id x48so5281557wes.25
        for <caml-list@inria.fr>; Fri, 27 Jun 2014 07:32:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=YC955QF28eokNm//z/EokP0ivvd9HdOSGqXRdoKqn/8=;
        b=EMgrG5mm/4nftos8fHT+W/XZAamJgZ8/o9eQMVsJJp2VpZK+4j00RXcYMNL5TFxZ21
         UX3m9GGTrplUaM0jIdcsAxfSV0/29Lay83yNPHiEMyQs12WSoR220WN3b+wOooEZEGiq
         1ybNxCk5FstGTipKXSCpOtJGF17w0EpIz+aRzOeRVzVNT0ANyOcxEA30p+FiqO1bbyAQ
         7hXWw77hRDfHcquCq0v/IhRTOExNXI34ab5M2fMUsVD+Z/+gYnjwi8yBN2qovGQnClK7
         GqYb5Dcz609S8Y3PbdK5tCrjoTukW0YxZ+xRT5T52aTxfIw7/pOFXTBCHSEwwe/MaDto
         Uf9g==
MIME-Version: 1.0
X-Received: by 10.180.84.226 with SMTP id c2mr7561628wiz.50.1403879565002;
 Fri, 27 Jun 2014 07:32:45 -0700 (PDT)
Received: by 10.216.219.193 with HTTP; Fri, 27 Jun 2014 07:32:44 -0700 (PDT)
In-Reply-To: <CAAxsn=GkMuQz_hNqRLxsRbRpK0GxOf_3ZFFq_02bkM_Y95h3Cg@mail.gmail.com>
References: <e9dba6f33347ae197b0fc1f1974001b0@lipn.univ-paris13.fr>
	<CAAxsn=GkMuQz_hNqRLxsRbRpK0GxOf_3ZFFq_02bkM_Y95h3Cg@mail.gmail.com>
Date: Fri, 27 Jun 2014 15:32:44 +0100
Message-ID: <CAAxsn=GZDi26PhFDaY=zu+NT3_=LQTBerPnM1qiqLbzHyCXp2w@mail.gmail.com>
From: Jeremy Yallop <yallop@gmail.com>
To: jean-vincent.loddo@lipn.univ-paris13.fr
Cc: Caml List <caml-list@inria.fr>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Caml-list] Memory leaks generated by Scanf.fscanf?

On 20 June 2014 14:01, Jeremy Yallop <yallop@gmail.com> wrote:
> Entries are added to the table for each input channel used for
> scanning, but there's no mechanism for removing entries.  This would
> be worth raising on Mantis.

   http://caml.inria.fr/mantis/view.php?id=6473