From: Paul Steckler <steck@stecksoft.com>
To: "Stéphane Glondu" <steph@glondu.net>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Segfaults with Dynlink with OCaml 3.11
Date: Mon, 23 Aug 2010 21:47:43 +1000 [thread overview]
Message-ID: <AANLkTikXgXz67h3kdUkFqa7=sAzFJQH7orceV65zd1uo@mail.gmail.com> (raw)
In-Reply-To: <4C725620.4070803@glondu.net>
On Mon, Aug 23, 2010 at 9:06 PM, Stéphane Glondu <steph@glondu.net> wrote:
> Does your real large program use C bindings? Are you able to reproduce
> the segfaults with pure OCaml code?
Yes, the large program has C bindings, including calls into dynamically loaded
.so files (Linux dynamic libraries). Anything I should look into for those?
Thanks,
-- Paul
next prev parent reply other threads:[~2010-08-23 11:48 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 [this message]
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 ` [Caml-list] " Damien Doligez
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='AANLkTikXgXz67h3kdUkFqa7=sAzFJQH7orceV65zd1uo@mail.gmail.com' \
--to=steck@stecksoft.com \
--cc=caml-list@yquem.inria.fr \
--cc=steph@glondu.net \
/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).