Issue #4265 (Printexc)

Issue #4265 (Printexc)

[Berke Durak]

[-- Attachment #1: Type: text/plain, Size: 549 bytes --]

On Sat, May 10, 2008 at 10:36 AM, Christophe TROESTLER <
Christophe.Troestler+ocaml@umh.ac.be<Christophe.Troestler%2Bocaml@umh.ac.be>>
wrote:

>
> Is it what you want: http://caml.inria.fr/mantis/view.php?id=4265 ?


That's a very nice thing to have.  Please, Xavier, could you expose the
loc_info type
and the get_exception_backtrace in the Printexc interface?  That would
allow,
for instance, to intelligently log the exceptions raised by the subthreads
in a
long-running web server without having to re-parse the string
representation.
-- 
Berke

[-- Attachment #2: Type: text/html, Size: 899 bytes --]

Re: [Caml-list] Issue #4265 (Printexc)

[Jake Donham]

[-- Attachment #1: Type: text/plain, Size: 940 bytes --]

2008/5/10 Berke Durak <berke.durak@gmail.com>:

> On Sat, May 10, 2008 at 10:36 AM, Christophe TROESTLER <
> Christophe.Troestler+ocaml@umh.ac.be<Christophe.Troestler%2Bocaml@umh.ac.be>>
> wrote:
>
> >
> > Is it what you want: http://caml.inria.fr/mantis/view.php?id=4265 ?
>
>
> That's a very nice thing to have.  Please, Xavier, could you expose the
> loc_info type
> and the get_exception_backtrace in the Printexc interface?  That would
> allow,
> for instance, to intelligently log the exceptions raised by the subthreads
> in a
> long-running web server without having to re-parse the string
> representation.
>

There is also a patch available (against 3.10.x) here

  http://skydeck.com/blog/programming/more-stack-traces-in-ocaml/

It exposes only the string representation, but it handles dynamically loaded
code (so e.g. can give stack traces in the toplevel), at the cost of keeping
debugging info in memory all the time.

Jake

[-- Attachment #2: Type: text/html, Size: 1601 bytes --]