caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Baelde <david.baelde@gmail.com>
To: "Stéphane Glondu" <steph@glondu.net>
Cc: Romain Beauxis <toots@rastageeks.org>, caml-list@inria.fr
Subject: Re: [Caml-list] Uncaught Unix_error.
Date: Thu, 18 Jun 2009 16:41:02 +0200	[thread overview]
Message-ID: <53c655920906180741m71893536he6ea5960c124dddf@mail.gmail.com> (raw)
In-Reply-To: <4A3A3E58.1040300@glondu.net>

On Thu, Jun 18, 2009 at 3:17 PM, Stéphane Glondu<steph@glondu.net> wrote:
> Such errors can also happen if you link the (same) Unix module twice:
> the exceptions raised by the first instance are not catchable by
> anything linked after the second instance.

Both liquidsoap and ocaml-duppy are compiled with -threads, so they
are using the same version of Unix. Duppy is not linked against Unix,
only requires it through ocamlfind. Could it be that ocamlfind (on
some versions) links Unix twice in liquidsoap? I did not know it was
even possible (except with Dynlink).

Also, note that the call to read that raises the error is from the
same module that tries to catch the exception.

I'm lost, I'd like to understand when the exception is registered: at
runtime initialization? In this case, only one should ever be
registered (at least it seems easy to enforce). Or is it statically
registered somehow?

-- 
David


  parent reply	other threads:[~2009-06-18 14:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 12:16 Romain Beauxis
2009-06-18 13:17 ` [Caml-list] " Stéphane Glondu
2009-06-18 13:28   ` Romain Beauxis
2009-06-18 14:41   ` David Baelde [this message]
2009-06-18 16:47     ` Jake Donham
2009-06-18 19:21     ` Stéphane Glondu
2009-06-18 20:16       ` David Baelde
2009-06-19 13:23       ` Romain Beauxis

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=53c655920906180741m71893536he6ea5960c124dddf@mail.gmail.com \
    --to=david.baelde@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=david.baelde@ens-lyon.org \
    --cc=steph@glondu.net \
    --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).