From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Patrick M Doane <patrick@watson.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCAMLRUNPARAM and backtraces
Date: Sat, 15 Sep 2001 10:15:32 +0200 [thread overview]
Message-ID: <20010915101532.B15229@pauillac.inria.fr> (raw)
In-Reply-To: <Pine.BSF.3.96.1010914233341.25152A-100000@fledge.watson.org>; from patrick@watson.org on Fri, Sep 14, 2001 at 11:42:46PM -0400
> I'm wondering if anyone might have any ideas why setting OCAMLRUNPARAM to
> include backtraces just doesn't work for me.
You need to compile and link with ocamlc -g, otherwise the bytecode
executable doesn't contain the required source<->code correspondence
information.
- Xavier Leroy
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-09-15 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-15 3:42 Patrick M Doane
2001-09-15 8:15 ` Xavier Leroy [this message]
2001-09-15 21:16 ` Patrick M Doane
[not found] <20010915004442.A10054@lakeland.eecs.harvard.edu>
2001-09-15 5:10 ` Patrick M Doane
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=20010915101532.B15229@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=patrick@watson.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;
as well as URLs for NNTP newsgroup(s).