caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Samuel Mimram <samuel.mimram@ens-lyon.org>
To: Caml List <caml-list@inria.fr>
Cc: Julien Cristau <jcristau@liafa.jussieu.fr>,
	Stefano Zacchiroli <zack@debian.org>
Subject: Module dependencies of bytecode executables
Date: Thu, 21 Sep 2006 09:39:57 +0200	[thread overview]
Message-ID: <451241CD.9090807@ens-lyon.org> (raw)

Hi list,

Is it somehow possible to extract the list of modules used by a bytecode
executable? "ocamldumpobj a.out | grep SETGLOBAL" seems to be a good
starting point but I don't know if it's reliable. Are the md5sums of the
imported interfaces still available?

Also, how can I determine which *.so will be dlopened by the executable?

Thanks!

Cheers,

Samuel.


             reply	other threads:[~2006-09-21  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21  7:39 Samuel Mimram [this message]
2006-09-21  9:26 ` [Caml-list] " Xavier Leroy
2006-09-21 10:08   ` Stefano Zacchiroli

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=451241CD.9090807@ens-lyon.org \
    --to=samuel.mimram@ens-lyon.org \
    --cc=caml-list@inria.fr \
    --cc=jcristau@liafa.jussieu.fr \
    --cc=zack@debian.org \
    /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).