caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Damien Doligez <damien.doligez@inria.fr>
To: caml-list caml-list <caml-list@yquem.inria.fr>
Cc: Paul Steckler <steck@stecksoft.com>
Subject: Re: [Caml-list] Re: Segfaults with Dynlink with OCaml 3.11
Date: Fri, 3 Sep 2010 16:59:02 +0200	[thread overview]
Message-ID: <4723F435-333B-4E7C-9226-2EE4F9D7B805@inria.fr> (raw)
In-Reply-To: <AANLkTinxtK-ScwAHUyZ7-UVPtKVFtu0FYFrjo5UraiZo@mail.gmail.com>


On 2010-08-25, at 06:00, Paul Steckler wrote:

> Today, I found the culprit.  Here's the pattern:
> 
>   dynamically load .cmxs file
>   query list mutated by .cmxs file      (* no problem *)
>   Gc.set { (Gc.get()) with Gc.minor_heap_size         = ...};
>   Gc.set { (Gc.get()) with Gc.major_heap_increment = ... };
>   query mutated list   (* segfault! *)
> 
> If I move the Gc.set's to the program initialization code, before the
> loading of dynamic code, no segfaults occur.

I bet the second Gc.set doesn't matter, and if you replace them with
Gc.minor () you get the same behaviour.

> Is this expected behavior?

Definitely not.  You should file a bug report here, preferably with
a complete repro case:
> Bug reports: http://caml.inria.fr/bin/caml-bugs


-- Damien


      reply	other threads:[~2010-09-03 14:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23 10:57 Paul Steckler
2010-08-23 11:06 ` [Caml-list] " Stéphane Glondu
2010-08-23 11:47   ` Paul Steckler
2010-08-23 12:05     ` Mark Shinwell
2010-08-23 12:12       ` Paul Steckler
2010-08-23 12:15         ` Daniel Bünzli
2010-08-23 12:28         ` Anil Madhavapeddy
2010-08-23 15:48         ` Stéphane Glondu
2010-08-25  4:00 ` Paul Steckler
2010-09-03 14:59   ` Damien Doligez [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=4723F435-333B-4E7C-9226-2EE4F9D7B805@inria.fr \
    --to=damien.doligez@inria.fr \
    --cc=caml-list@yquem.inria.fr \
    --cc=steck@stecksoft.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).