caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Thierry Bravier <thierry.bravier@dassault-aviation.fr>,
	caml-list@inria.fr
Cc: ac-ca@imaginet.fr, basile.starynkevitch@cea.fr, Emmanuel.Dorlet@cea.fr
Subject: Re: problem with ocamlmktop -output-obj
Date: Thu, 15 Oct 1998 19:22:43 +0200	[thread overview]
Message-ID: <19981015192243.14795@pauillac.inria.fr> (raw)
In-Reply-To: <3624D5BE.3060@dassault-aviation.fr>; from Thierry Bravier on Wed, Oct 14, 1998 at 06:47:58PM +0200

> I have encountered a problem while trying to build a toplevel
> (ocamlmktop) linked with
> - external C code and
> - ML code compiled as a C object (-output-obj and implicitely -custom).
> I have no problem when I build an ordinary batch (non-toplevel) program.
> Is this a limitation of the system or I am doing it wrong ?

Toplevels need access to their own symbol table, and they look inside
their executable file to find it.  The symbol table information is not
available if -output-obj is selected.

A regular bytecode executable file is composed of several sections:
code, data, symbols, and debug info.  Currently, only the first two
are available when a C object is generated instead of a regular
executable file.

For the same reasons, you can't debug a Caml program built with
-output-obj.

Hope this helps,

- Xavier Leroy





  reply	other threads:[~1998-10-16 11:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-14 16:47 Thierry Bravier
1998-10-15 17:22 ` Xavier Leroy [this message]
1998-10-16 10:40   ` Thierry Bravier
1998-10-26 16:03     ` Thierry Bravier
1998-10-30 10:17       ` Pascal Brisset
1998-10-30 17:56         ` problem with ocamlmktop (contd) Pascal Brisset
1998-11-03  9:32           ` Pascal Brisset
1998-11-04 17:56           ` Thierry Bravier
1998-11-04 16:12   ` problem with ocamlmktop -output-obj luther

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=19981015192243.14795@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=Emmanuel.Dorlet@cea.fr \
    --cc=ac-ca@imaginet.fr \
    --cc=basile.starynkevitch@cea.fr \
    --cc=caml-list@inria.fr \
    --cc=thierry.bravier@dassault-aviation.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;
as well as URLs for NNTP newsgroup(s).