caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alain.Frisch@ens.fr
To: Richard Jones <rich@annexia.org>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] CamlDL/Abstract pointers problem
Date: Thu, 29 Jan 2004 20:55:16 +0100 (MET)	[thread overview]
Message-ID: <Pine.SOL.4.44.0401292050490.23249-100000@clipper.ens.fr> (raw)
In-Reply-To: <20040129192641.GA12533@redhat.com>

On Thu, 29 Jan 2004, Richard Jones wrote:

> I'm pretty sure this bit of the manual is wrong, or at least I've not
> been able to make it work.  I don't have any definite proof of this,
> but my crashes stopped once I started wrapping up pointers in
> Abstract_tag.

One important thing to be aware of when you use "foreign" pointers is
that the Caml GC heap can grow at any time and span over existing
pointers. So you have to be careful to null foreign pointers when you free
the block they're pointing to.

Reference: http://pauillac.inria.fr/~doligez/caml-guts/Fahndrich99.txt

-- Alain

-------------------
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


  reply	other threads:[~2004-01-29 19:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 13:06 ronniec95
2004-01-29 15:02 ` Richard Jones
2004-01-29 15:52   ` ronniec95
2004-01-29 16:32     ` art yerkes
2004-01-29 19:04   ` skaller
2004-01-29 19:26     ` Richard Jones
2004-01-29 19:55       ` Alain.Frisch [this message]
2004-01-29 20:24         ` Richard Jones
2004-01-29 23:07           ` David Brown
2004-01-30  0:20           ` Jacques Garrigue
2004-01-30  7:04             ` Brian Hurt
2004-01-30 15:36               ` Jacques Garrigue
2004-01-30 16:52                 ` Brian Hurt
2004-01-30 20:56               ` skaller

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=Pine.SOL.4.44.0401292050490.23249-100000@clipper.ens.fr \
    --to=alain.frisch@ens.fr \
    --cc=caml-list@inria.fr \
    --cc=rich@annexia.org \
    /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;
as well as URLs for NNTP newsgroup(s).