From: Luca Pascali <pasckosky2000@yahoo.it>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Native executable symtable
Date: Thu, 11 Nov 2004 12:09:06 +0100 [thread overview]
Message-ID: <41934852.8020102@yahoo.it> (raw)
In-Reply-To: <017f01c4c7da$be6aba40$ef01a8c0@warp>
Nicolas Cannasse wrote:
> [...]
>
>I would say this is very difficult since it depends on linker used to
>produce executable.
>For bytecode things are always very easy since the CMO/CMA are just
>Marshalled data of some ocaml data structure. As always, it get complicated
>when you deal with system specificity issues.
>
>Regards,
>Nicolas Cannasse
>
>
I can say that informations about signatures of used modules are present
in both the bytecode and native executables.
I saw a macroscopical difference between those two results is that in
the bytecode compiler, at the end of the file, there is a TOC section
that gives informations about the header sections. One of this sections
(named CRCS) is the one with the signatures.
In the native compilation, these informations are not lost (at least
with Ocaml 3.07+2 under Linux. Correct me if I am wrong).
But how can we access those informations?
Module Sys gives a mutable value that says if we are running under a
toplevel or not (Sys.interactive), too bad there's not something that
says us if we are using a bytecode compiled application or not.
A method can be looking for the TOC for knowing if the application is
bytecode or native.
In case of bytecode file, the TOC says us where the CRCS are located
into the file. But at which offset we can found those CRCS in the native
code compiled?
Thanks in advance
Luca
--
*********************************************************************
Luca Pascali
luca@barettadeit.com
asxcaml-guru@barettadeit.com
http://www.barettadeit.com/
Baretta DE&IT
A division of Baretta SRL
tel. 02 370 111 55
fax. 02 370 111 54
Our technology:
http://www.asxcaml.org/
http://www.freerp.org/
next prev parent reply other threads:[~2004-11-11 11:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 10:18 Alex Baretta
2004-11-11 10:39 ` [Caml-list] " Nicolas Cannasse
2004-11-11 11:09 ` Luca Pascali [this message]
2004-11-11 11:55 ` Keith Wansbrough
2004-11-11 12:09 ` Luca Pascali
2004-11-11 12:28 ` Keith Wansbrough
2004-11-11 12:42 ` Luca Pascali
2004-11-11 16:09 ` Richard Jones
2004-11-20 15:44 ` Luca Pascali
2004-11-20 16:03 ` malc
2004-11-20 18:01 ` Alex Baretta
2004-11-20 18:06 ` malc
2004-11-20 18:53 ` Alex Baretta
2004-11-20 19:17 ` malc
2004-11-20 20:07 ` Ritesh Kumar
2004-11-20 22:43 ` The madness of ignoring people Vincenzo Ciancia
2004-11-20 23:10 ` [Caml-list] " malc
2004-11-20 23:25 ` Vincenzo Ciancia
2004-11-21 12:51 ` skaller
2004-11-21 14:14 ` Vincenzo Ciancia
2004-11-21 14:30 ` malc
2004-11-21 3:37 ` [Caml-list] Native executable symtable skaller
2004-11-21 15:59 ` Richard Jones
2004-11-21 20:29 ` skaller
2004-11-21 20:39 ` malc
2004-11-21 23:30 ` Richard W.M. Jones
2004-11-22 3:25 ` skaller
2004-11-21 20:42 ` Jean-Marie Gaillourdet
2004-11-21 18:31 ` Ritesh Kumar
2004-11-21 23:33 ` Richard Jones
2004-11-21 21:15 ` skaller
2004-11-11 16:23 ` David Brown
2004-11-11 17:27 ` Xavier Leroy
2004-11-11 18:48 ` Alex Baretta
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=41934852.8020102@yahoo.it \
--to=pasckosky2000@yahoo.it \
--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