caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Michael Hicks <mwh@dsl.cis.upenn.edu>
To: caml-list@inria.fr
Subject: dynamic loading of Caml bytecode
Date: Mon, 8 Nov 1999 11:07:23 -0500 (EST)	[thread overview]
Message-ID: <199911081607.LAA27012@codex.cis.upenn.edu> (raw)


I wonder if anyone could elaborate for me on the safety of dynamically
loaded Ocaml bytecode?  Is it possible to load bytecode that is not
well-formed or type-correct (thus resulting in a core-dump or other
misbehavior at runtime)?  I understand that interfaces are checked for
consistency using MD5 hashes, but I'm curious about the internal consistency
of the bytecode file itself.

Thanks,
Mike

-- 
Michael Hicks
Ph.D. Candidate, the University of Pennsylvania
http://www.cis.upenn.edu/~mwh            mailto://mwh@dsl.cis.upenn.edu
"People are often unreasonable, illogical, and self-centered;
Forgive them anyway." -- Mother Teresa



             reply	other threads:[~1999-11-08 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-08 16:07 Michael Hicks [this message]
1999-11-11 21:01 ` Xavier Leroy

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=199911081607.LAA27012@codex.cis.upenn.edu \
    --to=mwh@dsl.cis.upenn.edu \
    --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).