From: Nicolas Boulay <nicolas@boulay.name>
To: John Whitington <john@coherentgraphics.co.uk>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] ANN: exn-source - exception backtraces with source code printing
Date: Mon, 20 Oct 2014 11:15:27 +0200 [thread overview]
Message-ID: <CAH+PdrDEtLw5WnAU4Zp3pKSC9+ZJnZ2T1jujjWG=L7dAFb_vQg@mail.gmail.com> (raw)
In-Reply-To: <5443FCE6.50206@coherentgraphics.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]
Very nive project !
May a suggest a different result presentation ? Most of the time, only name
of the function called are usefull, its more compact than 5 lines arround
the call site.
One other very important feature will be the parameter value of the
function call. It's value could be serialised on fixe size (<20 characters
by default). On a tricky bug, the next step is to print such value, so you
save time to print it with the function call.
2014-10-19 20:03 GMT+02:00 John Whitington <john@coherentgraphics.co.uk>:
> Hi,
>
> OCaml 4.02 has new facilities for installing a new backtrace handler, and
> processing the back trace symbolically. As a little proof of concept, I've
> built a package which you can add to any project to get backtrace with
> source code printed and highlighted:
>
> https://github.com/johnwhitington/exn-source
>
> Here's the start of a backtrace:
>
> http://www.coherentpdf.com/exnsource.png
>
> By default, it prints five lines either side, and looks the current
> directory for source code. But as one can see from the screenshot, one can
> add /usr/local/lib/ocaml to get stdlib source and so on...
>
> It's somewhat difficult to test this kind of thing (we can't use
> exceptions at all inside a backtrace handler, for example), so I'm
> appealing for help. Attach exn-source to your code and let me know how you
> get on...
>
> Thanks,
>
> --
> John Whitington
> Director, Coherent Graphics Ltd
> http://www.coherentpdf.com/
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 2695 bytes --]
next prev parent reply other threads:[~2014-10-20 9:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 18:03 John Whitington
2014-10-19 18:26 ` Gabriel Scherer
2014-10-19 18:55 ` John Whitington
2014-10-19 19:05 ` Gabriel Scherer
[not found] ` <54441347.904@coherentgraphics.co.uk>
2014-10-19 19:50 ` Gabriel Scherer
2014-10-20 9:15 ` Nicolas Boulay [this message]
2014-10-20 9:35 ` Peter Zotov
2014-10-20 11:52 ` John Whitington
2014-10-20 12:06 ` Peter Zotov
2014-10-20 12:15 ` Francois Berenger
2014-10-20 18:28 ` Török Edwin
2014-10-23 8:32 ` John Whitington
2014-10-23 11:48 ` Sébastien Hinderer
2014-10-23 16:43 ` Gabriel Scherer
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='CAH+PdrDEtLw5WnAU4Zp3pKSC9+ZJnZ2T1jujjWG=L7dAFb_vQg@mail.gmail.com' \
--to=nicolas@boulay.name \
--cc=caml-list@inria.fr \
--cc=john@coherentgraphics.co.uk \
/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