caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
To: caml-list@inria.fr
Subject: caml_alloc + 64 bits - caml_alloc.h
Date: Tue, 13 Jan 2009 05:51:16 +0100	[thread overview]
Message-ID: <20090113045116.GA646@yquem.inria.fr> (raw)

Hi everybody,

Possibly useful information. Is it already known?

When using calls to "caml_alloc" in a 64 bits architecture without
having included "caml/alloc.h", it raises "Segmentation fault" at
execution time.

Notice that I got no warning at compilation time for using caml_alloc
without a definition stub.

In 32 bits architecture, I never had any problem with that.

Morality:
   Don't forget to #include "caml/alloc.h" in your C programs
   if you alloc OCaml things!

-- 
Daniel de Rauglaudre
http://pauillac.inria.fr/~ddr/


             reply	other threads:[~2009-01-13  4:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13  4:51 Daniel de Rauglaudre [this message]
2009-01-13  4:58 ` [Caml-list] " Erik de Castro Lopo
2009-01-13  5:15   ` Daniel de Rauglaudre
2009-01-13  9:37 ` malc
2009-01-13 10:26   ` Olivier Andrieu

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=20090113045116.GA646@yquem.inria.fr \
    --to=daniel.de_rauglaudre@inria.fr \
    --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;
as well as URLs for NNTP newsgroup(s).