From: Richard Jones <rich@annexia.org>
To: caml-list@inria.fr
Subject: [Caml-list] mod_caml 0.4 & continuing dynlink problems
Date: Sun, 10 Aug 2003 16:46:09 +0100 [thread overview]
Message-ID: <20030810154609.GA29522@redhat.com> (raw)
On the links below you'll find mod_caml 0.4. You'll also need the
associated patch against the clean ocaml 3.06 tree.
The version still doesn't work. This time, following advice from David
Gurr, I put the C primitives from the .so file into the table of
primitives (by hacking Dynlink again to call Dynlink.set_prim_table).
OCaml now recognises them but doesn't bind them to the correct values.
I can't understand how this binding happens with external references.
I tried breakpointing various obvious candidates, eg.,
dynlink.c:lookup_primitive, build_primitive_table; but these never
seem to be called as far as I can see.
The result is that when the code tries to call the external C function
mod_caml_request_uri, it jumps to an apparently random address and
crashes.
Ideas?
Rich.
http://www.annexia.org/tmp/ocaml-3.06.dynlink.patch2
http://www.annexia.org/tmp/mod_caml-0.4.tar.gz
--
Richard Jones. http://www.annexia.org/ http://freshmeat.net/users/rwmj
Merjis Ltd. http://www.merjis.com/ - all your business data are belong to you.
MAKE+ is a sane replacement for GNU autoconf/automake. One script compiles,
RPMs, pkgs etc. Linux, BSD, Solaris. http://www.annexia.org/freeware/makeplus/
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2003-08-10 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-10 15:46 Richard Jones [this message]
2003-08-10 22:13 ` Daniel Bünzli
2003-08-11 8:18 ` Richard Jones
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=20030810154609.GA29522@redhat.com \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
/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).