Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Francois Rouaix <Francois.Rouaix@inria.fr>
To: Lyn A Headley <laheadle@midway.uchicago.edu>
Cc: caml-list@inria.fr
Subject: Re: bytecode "disassembler"?
Date: Tue, 10 Jun 1997 14:21:02 +0200	[thread overview]
Message-ID: <199706101221.OAA30703@madiran.inria.fr> (raw)
In-Reply-To: Your message of "Mon, 09 Jun 1997 20:19:51 CDT." <199706100119.UAA01017@kimbark.uchicago.edu>

> I thought it might be handy to be able to disassemble a compiled
> object file to see how the ocaml compiler handles certain constructs,
> thereby obtaining a better feel for the machine's instruction
> set.  Before I start writing code, I wonder, has anyone else attempted
> such a thing?
It's already available in the tools directory of the distribution.
Simply compile it (make dumpobj) and you're done. It decompiles .cmo files.

--f







      reply	other threads:[~1997-06-12  8:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-06-10  1:19 Lyn A Headley
1997-06-10 12:21 ` Francois Rouaix [this message]

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=199706101221.OAA30703@madiran.inria.fr \
    --to=francois.rouaix@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=laheadle@midway.uchicago.edu \
    /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