From: Xavier Leroy <xavier.leroy@inria.fr>
To: Lex Stein <stein@eecs.harvard.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] exception stack trace from --output-obj'ed Caml code
Date: Mon, 16 Jun 2003 17:05:03 +0200 [thread overview]
Message-ID: <20030616170503.A9308@pauillac.inria.fr> (raw)
In-Reply-To: <Pine.BSF.4.51.0306152252090.1723@bowser.eecs.harvard.edu>; from stein@eecs.harvard.edu on Sun, Jun 15, 2003 at 10:59:17PM -0400
> Hi, I have OCAMLRUNPARAM set to b=1 and have compiled and linked with the
> -g flag. I am doing linking with gcc because I have a C main and C
> objects. The Caml code is compiled with the -output-obj flag to create a
> .o that gcc links with. Unfortunately, I'm not seeing exception stack
> traces for uncaught exceptions. For example, I get:
>
> Fatal error: exception Invalid_argument("String.get")
> (Program not linked with -g, cannot print stack backtrace)
This is a known limitation of -output-obj: the debug info that is used
to generate stack backtraces is not included in the generated object file.
> Is there a way to solve this while continuing to use -output-obj to
> generate a C-like object for gcc to link against ?
No, not currently.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2003-06-16 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 2:59 Lex Stein
2003-06-16 15:05 ` Xavier Leroy [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=20030616170503.A9308@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=stein@eecs.harvard.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