caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Markus Mottl <mottl@miss.wu-wien.ac.at>, OCAML <caml-list@inria.fr>
Subject: Re: ocamldebug must not be stripped!
Date: Thu, 25 Jun 1998 11:43:09 +0200	[thread overview]
Message-ID: <19980625114309.54105@pauillac.inria.fr> (raw)
In-Reply-To: <199806220948.LAA28374@miss.wu-wien.ac.at>; from Markus Mottl on Mon, Jun 22, 1998 at 11:48:44AM +0100

> I have just found out that "ocamldebug" itself must not be stripped in
> order to work (at least under i686 - Linux 2.0.30 and Alpha - Digital
> Unix 4.0d). I didn't find this anywhere in the documentation.
> Does "ocamldebug" really need its own debug information or is this a bug?
> It will probably need it in any case... ;-)
> 
> Do the other programs need their debug information? Until now I have
> not encountered any problems, but who knows...

All executables generated by "ocamlc -custom" must not be stripped.

The reason is that they are composed of a C executable (the custom
runtime system) concatenated with the OCaml bytecode for the program.
The C executable looks at "itself" (the file it comes from) to load
the bytecode.

"strip" on most Unix machines just discards the C debugging
information as well as everything that follows it, thus discarding the
bytecode as well.

ocamldebug is just an instance of the general case, since it is
produced by "ocamlc -custom".

- Xavier Leroy





  reply	other threads:[~1998-06-25 23:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-22 10:48 Markus Mottl
1998-06-25  9:43 ` Xavier Leroy [this message]
     [not found] <13711.22440.102506.717388@pc84.lri.fr>
1998-06-24 16:49 ` Markus Mottl

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=19980625114309.54105@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=mottl@miss.wu-wien.ac.at \
    /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).