Version française
Home     About     Download     Resources     Contact us    
Browse thread
Seeking exception source
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: skaller <skaller@u...>
Subject: Re: [Caml-list] Seeking exception source
On Tue, 2005-11-08 at 19:06 +0900, Nicolas Cannasse wrote:
> >>> I am occasionally annoyed by Not_found propagating to my
> >>> top level function .. meaning the error could be anywhere
> >>> at all in my program.
> >>
> >>
> >> At that time the best is to run your program in bytecode with debug infos 
> >> using ocamlrun -b so you'll get full backtrace informations. 

> >
> > In many cases this is completely inadequate. The AS/Xcaml application 
> > server, for example, cannot terminate on an uncaught exception in a 
> > program module. 

> Yes I agree, this is not all the time easy to get exceptions backtraces 

However all of this misses what I seek, which is a way
to *manually* add backtrace information.

In addition to the annoying errors leading to Not_found
exceptions, there are other exceptions which are supposed
to be caught and sometimes leak, and in addition, there
are exceptions which are thrown when there are USER errors,
and these are caught in the top level and reported.
That's where I want the backtrace .. I want to unwind
it manually.



-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net