From: Guillaume Yziquel <guillaume.yziquel@citycable.ch>
To: ygrek <ygrekheretix@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Wrapping C code using pthread.
Date: Sun, 27 Dec 2009 22:33:33 +0100 [thread overview]
Message-ID: <4B37D2AD.5000600@citycable.ch> (raw)
In-Reply-To: <20091227232724.f95c1105.ygrekheretix@gmail.com>
ygrek a écrit :
> On Sun, 27 Dec 2009 13:19:36 +0100
> Guillaume Yziquel <guillaume.yziquel@citycable.ch> wrote:
>
>> In fact, my trouble is that when things are compiled to native code, it
>> works fine. However, things get screwed up when compiled to bytecode,
>> resulting in a segfault.
>>
>> Are pthreads compatible with OCaml bytecode?
>
> I believe so. Could you post some code and instructions how to build for investigation?
I'm working on it. Will look at ocamlforge for this purpose.
I now think, however, that it's not a thread issue. MonetDB loads
dynamically at startup some other libraries for its own low-level
language, MAL (for MonetDB Assembly Language). I believe this kind of
dynamic loading works fine in native code, but doesn't in bytecode.
I've got no issues in native code at all... Only with bytecode.
Haven't located the place in MonetDB where this dynamic loading happens,
so it's just conjectures for now.
If someone knows how to use gdb on a bytecode executable to locate the
segfault in MonetDB's .so file, I'd be quite happy to know.
All the best,
--
Guillaume Yziquel
http://yziquel.homelinux.org/
next prev parent reply other threads:[~2009-12-27 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-25 20:57 Guillaume Yziquel
2009-12-27 9:42 ` [Caml-list] " ygrek
2009-12-27 12:19 ` Guillaume Yziquel
2009-12-27 21:27 ` ygrek
2009-12-27 21:33 ` Guillaume Yziquel [this message]
2009-12-29 3:39 ` Jake Donham
2009-12-30 23:50 ` Guillaume Yziquel
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=4B37D2AD.5000600@citycable.ch \
--to=guillaume.yziquel@citycable.ch \
--cc=caml-list@inria.fr \
--cc=ygrekheretix@gmail.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