From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: "Krishnaswami, Neel" <neelk@cswcasa.com>
Cc: "'caml-list@inria.fr'" <caml-list@inria.fr>
Subject: Re: [Caml-list] Backtraces in the interactive interpreter?
Date: Fri, 29 Jun 2001 09:35:27 +0200 [thread overview]
Message-ID: <20010629093527.A29066@pauillac.inria.fr> (raw)
In-Reply-To: <B1E4D3274D57D411BE8400D0B783FF322E8629@exchange1.cswv.com>; from neelk@cswcasa.com on Thu, Jun 28, 2001 at 03:08:56PM -0400
> I do a lot of Objective Caml development with the toplevel under
> Emacs, and I'd like to know how I can enable backtraces in it.
This is currently not supported, and would actually be quite hard to
implement. The backtrace mechanism is highly dependent on standalone
executables, with the debugging info being "linked in" the executable.
> I tried byte-compiling my libraries with '-g', but this makes
> the ocaml toplevel dump core when I try to #load them.
I'm very, very surprised by this. It works fine here. If you can
reproduce the problem, please report it (along with a recipe for
reproducing it) to caml-bugs@inria.fr.
scott@chronis.pobox.com suggested:
> set your environmental variable OCAMLRUNPARAM to "b=1" before you
> start emacs.
This won't do. At best, it would report a stack backtrace when the
ocaml toplevel itself dies on an uncaught exception (which should
never happen), but not backtraces for user-defined code.
- 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
prev parent reply other threads:[~2001-06-29 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 19:08 Krishnaswami, Neel
2001-06-28 19:42 ` scott
2001-06-29 7:35 ` 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=20010629093527.A29066@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=neelk@cswcasa.com \
/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).