From: David Brown <caml-list@davidb.org>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: Basile STARYNKEVITCH <basile@starynkevitch.net>,
David Brown <caml-list@davidb.org>,
Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Memory leak with native code.
Date: Sat, 7 Dec 2002 13:52:43 -0800 [thread overview]
Message-ID: <20021207215243.GA6091@opus.davidb.org> (raw)
In-Reply-To: <20021207114236.B23052@pauillac.inria.fr>
On Sat, Dec 07, 2002 at 11:42:36AM +0100, Xavier Leroy wrote:
> That would explain why a program compiled to native code uses more
> stack space than when compiled to byte code. However, there is no
> evidence that David's problem is related to stack space.
It gets even stranger. After doing a make clean, and recompiling
everything, the memory leak now appears to be gone.
Dave
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2002-12-07 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 18:48 David Brown
2002-12-05 19:14 ` Markus Mottl
2002-12-05 20:31 ` Basile STARYNKEVITCH
2002-12-07 10:42 ` Xavier Leroy
2002-12-07 21:52 ` David Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021207215243.GA6091@opus.davidb.org \
--to=caml-list@davidb.org \
--cc=basile@starynkevitch.net \
--cc=caml-list@inria.fr \
--cc=xavier.leroy@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox