From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: David Mentre <David.Mentre@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Finding how and where an exception is raised
Date: Fri, 27 Jul 2001 10:21:59 +0200 [thread overview]
Message-ID: <20010727102159.A17912@pauillac.inria.fr> (raw)
In-Reply-To: <qtln161115v.fsf@pochi.inria.fr>; from David.Mentre@inria.fr on Thu, Jul 19, 2001 at 03:47:08PM +0200
> I would like to find how and where an exception is raised by printing a
> stack backtrace (something like Java Throwable.printStackTrace()).
>
> It seems to be impossible in plain ocaml. I could set the environment
> variable OCAMLRUNPARAM="b=1" and let the exception escape the program,
> but I would only get one exception.
Right. I think the "stack backtrace" mechanism of OCaml could be
extended to provide what you need. I'll look into this after 3.02 is
out.
Best wishes,
- 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-07-27 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 13:47 David Mentre
2001-07-27 8:21 ` 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=20010727102159.A17912@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=David.Mentre@inria.fr \
--cc=caml-list@inria.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