From: Richard Jones <rich@furbychan.annexia.org>
To: Jon Harrop <jdh30@hermes.cam.ac.uk>
Cc: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] caml_oldify_local_roots crashes
Date: Thu, 30 Dec 2004 22:41:11 +0000 [thread overview]
Message-ID: <20041230224111.GA9369@furbychan.cocan.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0412260428100.23835@hermes-1.csi.cam.ac.uk>
On Sun, Dec 26, 2004 at 04:35:53AM +0000, Jon Harrop wrote:
> On Sat, 25 Dec 2004, haiku.issa wrote:
> >Everything worked fine until I added a subfunction that simply
> >merges two int lists.
> I am no expert on this but I believe this implies that your interfacing
> between C and OCaml was already broken. Almost certainly something to do
> with the GC.
It often helps to add lots of calls to Gc.full_major () to your code.
One of these will crash, telling you that between that call and the
previous one, you did something bad to the heap.
Rich.
next prev parent reply other threads:[~2004-12-30 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-25 13:11 haiku.issa
2004-12-26 4:35 ` [Caml-list] " Jon Harrop
2004-12-30 22:41 ` Richard Jones [this message]
2005-01-02 19:00 Zakath
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=20041230224111.GA9369@furbychan.cocan.org \
--to=rich@furbychan.annexia.org \
--cc=caml-list@yquem.inria.fr \
--cc=jdh30@hermes.cam.ac.uk \
/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