From: Richard Jones <rich@annexia.org>
To: Jonathan Roewen <jonathan.roewen@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] help with caml_stat_alloc
Date: Mon, 24 Jul 2006 09:56:00 +0100 [thread overview]
Message-ID: <20060724085600.GB11739@furbychan.cocan.org> (raw)
In-Reply-To: <73347253780-BeMail@beos>
On Mon, Jul 24, 2006 at 12:50:32AM -0700, Jonathan Roewen wrote:
> I'm trying to allocate some memory outside of the caml heap, and I
> think caml_stat_alloc is the right function to use. Anyways, it's
> generating seg-faults, so I'm hoping someone can help me fix my
> implementation.
What was wrong with malloc?
Have a look at ocamlode (http://merjis.com/developers/ocamlode), file
ode_c.c for some functions which wrap external pointers in custom
blocks.
Rich.
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com
next prev parent reply other threads:[~2006-07-24 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 7:50 Jonathan Roewen
2006-07-24 8:56 ` Richard Jones [this message]
2006-07-24 10:13 ` Olivier Andrieu
2006-07-24 11:39 ` Anatoly Zaretsky
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=20060724085600.GB11739@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=jonathan.roewen@gmail.com \
/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).