Le jeudi 18 juin 2009 21:21:20, Stéphane Glondu a écrit :
> > 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?
>
> T
Thanks for all the details. The application does have support for
dynamically loading plugins but it's basically never used. We should
double check with the user (we can't reproduce) maybe he's loading
something funny...
--
David
___
Caml-list mailing l
David Baelde a écrit :
> 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 i
On Thu, Jun 18, 2009 at 7:41 AM, David Baelde wrote:
> 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 shoul
On Thu, Jun 18, 2009 at 3:17 PM, Stéphane Glondu 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
Le jeudi 18 juin 2009 15:17:12, Stéphane Glondu a écrit :
> > We believe that the issue is raised because the module that uses
> > Unix.read is compiled with one of unix or threads and the application
> > using that module with the other one.
>
> Such errors can also happen if you link the (same) U
Romain Beauxis a écrit :
> We have had a strange bug report on our code. Somehow, an Unix.Unix_error
> exception was not caught while it ought to be. See:
> http://savonet.rastageeks.org/ticket/269
> [...]
> We believe that the issue is raised because the module that uses Unix.read is
> compile
Hi all !
We have had a strange bug report on our code. Somehow, an Unix.Unix_error
exception was not caught while it ought to be. See:
http://savonet.rastageeks.org/ticket/269
We have precisely characterized the issue in the code, and we would like to
understand its possible origin.
