From: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Val_int vs caml_copy_nativeint
Date: Wed, 10 Aug 2011 08:53:57 +1000 [thread overview]
Message-ID: <20110810085357.73059efd1f39ef2e9466ccd3@mega-nerd.com> (raw)
In-Reply-To: <20110809113359.c306a95842c0c86ea160025d@mega-nerd.com>
Erik de Castro Lopo wrote:
> This is strange, it wasn't declared with a CAMLlocal macro and it
> was working, but if I do declare it with one the program segfaults
> during garbage collection (caml_oldify_local_roots).
Ok, with the help of someone off list I've sorted this out to
my satisfaction. Things learned:
a) In the C stub function, the call to CAMLParamN must be the
first thing in the function, followed by any CAMLlocalN
declarations. These should even occur before before any
declarations of local C variables.
b) caml_copy_nativeint creates a boxed native int (either Int32.t
or Int64.t) not an unboxed Ocaml int. To create an unboxed
Ocaml int, Val_int() is the correct macro.
Thanks to all that responded.
Erik
--
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/
next prev parent reply other threads:[~2011-08-09 22:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 3:15 Erik de Castro Lopo
2011-08-08 3:48 ` Romain Beauxis
2011-08-08 3:59 ` Guillaume Yziquel
2011-08-08 7:49 ` Erik de Castro Lopo
2011-08-08 3:53 ` Guillaume Yziquel
2011-08-08 7:46 ` Erik de Castro Lopo
2011-08-08 8:03 ` Guillaume Yziquel
2011-08-08 9:17 ` Mathias Kende
2011-08-08 17:24 ` Xavier Leroy
2011-08-09 1:33 ` Erik de Castro Lopo
2011-08-09 1:40 ` Romain Beauxis
2011-08-09 8:44 ` David Allsopp
2011-08-09 10:07 ` malc
2011-08-09 10:43 ` David Allsopp
2011-08-09 22:53 ` Erik de Castro Lopo [this message]
2011-08-10 6:43 ` Gabriel Scherer
2011-08-08 5:20 ` malc
2011-08-08 6:01 ` Guillaume Yziquel
2011-08-08 6:22 ` malc
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=20110810085357.73059efd1f39ef2e9466ccd3@mega-nerd.com \
--to=mle+ocaml@mega-nerd.com \
--cc=caml-list@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