From: blue storm <bluestorm.dylc@gmail.com>
To: Lukasz Stafiniak <lukstafi@gmail.com>
Cc: Nicolas Pouillard <nicolas.pouillard@gmail.com>, caml-list@inria.fr
Subject: Re: [Caml-list] Static exception analysis or alternative to using exceptions
Date: Mon, 31 May 2010 23:42:50 +0200 [thread overview]
Message-ID: <AANLkTikVbWZYbnyM6mN7Ho8omsA6jjGLACtgJAw7f6ps@mail.gmail.com> (raw)
In-Reply-To: <AANLkTil7kXzh-dJ6rEohK7OvQuVqz3bc6ToEdmZTbGa2@mail.gmail.com>
> I use a syntax extension that catches "Not_found" and raises a failure
> instead, with the source location of the "real" offending call. I do
> this mostly because OUnit catches exceptions so backtraces are of no
> use.
I have encoutered the same problem and resolved it with explicit
backtrace handling in Printexc. I use the following function wrapper :
let verbose_func func x =
try func x with exn ->
Printf.printf "Test error %s\n%!" (Pinrtexc.to_string exn);
Printf.printf "%s\n%!" (Printexc.get_backtrace ());
raise exn in
next prev parent reply other threads:[~2010-05-31 21:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 16:15 Hans Ole Rafaelsen
2010-05-27 9:34 ` [Caml-list] " Alain Frisch
2010-05-27 17:01 ` Richard Jones
2010-05-27 21:13 ` Dario Teixeira
2010-05-31 14:36 ` Goswin von Brederlow
2010-05-31 15:00 ` Florent Ouchet
2010-05-31 17:24 ` David Allsopp
2010-05-31 20:51 ` Török Edwin
2010-06-08 9:16 ` Goswin von Brederlow
2010-05-31 19:30 ` Nicolas Pouillard
2010-05-31 20:57 ` Lukasz Stafiniak
2010-05-31 21:42 ` blue storm [this message]
2010-05-31 19:36 ` Christophe Raffalli
2010-05-26 17:30 Dario Teixeira
2010-05-26 21:10 ` Hans Ole Rafaelsen
2010-05-27 3:37 ` Jacques Le Normand
2010-05-27 8:08 ` Florent Ouchet
2010-05-27 8:50 ` Eray Ozkural
2010-05-27 11:10 ` Florent Ouchet
2010-05-27 8:54 ` David Allsopp
2010-05-27 9:11 ` Mark Shinwell
2010-05-27 9:29 ` David Allsopp
2010-05-27 9:12 ` Daniel Bünzli
2010-05-27 9:19 ` David Allsopp
2010-05-27 9:15 ` David Rajchenbach-Teller
2010-05-27 13:56 ` Hezekiah M. Carty
2010-06-01 19:08 Peter Ronnquist
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=AANLkTikVbWZYbnyM6mN7Ho8omsA6jjGLACtgJAw7f6ps@mail.gmail.com \
--to=bluestorm.dylc@gmail.com \
--cc=caml-list@inria.fr \
--cc=lukstafi@gmail.com \
--cc=nicolas.pouillard@gmail.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