From: "Stéphane Glondu" <steph@glondu.net>
To: Romain Beauxis <toots@rastageeks.org>
Cc: caml-list@inria.fr, smimram@debian.org
Subject: Re: [Caml-list] toplevel not executed: Bug ?
Date: Wed, 03 Sep 2008 23:56:29 +0200 [thread overview]
Message-ID: <48BF080D.7070600@glondu.net> (raw)
In-Reply-To: <200809031808.55821.toots@rastageeks.org>
Romain Beauxis wrote:
> I've encountered a strange bug while preparing a caml module with C function.
> Depending on the execution of a caml-defined function, the toplevel is
> evaluated or not, leading to a segfault when calling a caml callback from C.
> [...]
I don't know whether this is a bug, but I have an explanation.
At linking phase, module Test is not linked in because it is not used.
When you use "-linkall", the segfault disappear.
Module Test is considered unused because the inferred interface for
module Test records that f is an external. You can force the usage of
module Test by providing your own .mli, where f is abstracted. When you
do so, the segfault disappear (even without -linkall).
HTH,
--
Stéphane Glondu
prev parent reply other threads:[~2008-09-03 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 16:08 Romain Beauxis
2008-09-03 21:56 ` Stéphane Glondu [this message]
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=48BF080D.7070600@glondu.net \
--to=steph@glondu.net \
--cc=caml-list@inria.fr \
--cc=smimram@debian.org \
--cc=toots@rastageeks.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).