From: Jonathan Roewen <jonathan.roewen@gmail.com>
To: david.baelde@ens-lyon.org
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] disassembling cmo files
Date: Wed, 7 Dec 2005 23:02:24 +1300 [thread overview]
Message-ID: <ad8cfe7e0512070202n202581dbrd46938870ae3c7f5@mail.gmail.com> (raw)
In-Reply-To: <53c655920512070152jbafa79aw@mail.gmail.com>
On 12/7/05, David Baelde <david.baelde@gmail.com> wrote:
> Hi,
>
> A simple and interesting way to learn about the bytecode is the
> -dinstr option of ocamlc and ocaml toplevel. It dumps a human-readable
> version of the produced bytecode. Similarly, there is -dlambda.
Yes, I've used that before, but those are pseudo instructions .. not
what actually goes into a bytecode file I believe.
> IIRC, the ocaml/tools directory (from Ocaml CVS)
> contains a dumpobj.ml which should do it.
I tried compiling, but it complains about an undefined field in
debug_event, line 391 (ocaml3.09.0).
Jonathan
next prev parent reply other threads:[~2005-12-07 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 7:45 Jonathan Roewen
2005-12-07 8:55 ` basile
2005-12-07 9:52 ` David Baelde
2005-12-07 10:02 ` Jonathan Roewen [this message]
2005-12-07 10:11 ` Oliver Bandel
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=ad8cfe7e0512070202n202581dbrd46938870ae3c7f5@mail.gmail.com \
--to=jonathan.roewen@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=david.baelde@ens-lyon.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