On 2007-01-22 21:54, Denis Bueno wrote:
> I found some > 6 year old threads on this list
> (http://caml.inria.fr/pub/ml-archives/caml-list/2000/07/5a1aa1b9873679a2bf87fce5c55f342f.en.html)
> having to do with the fact that you couldn't get backtraces on caught
> exceptions without using camlp4.
> Is this still the case?

Taken from the latest Caml Weekly News, for the week of January 16 to 23, 2007 :

>> ========================================================================
>> 8) native-code stack backtraces
>> Archive: <http://groups.google.com/group/fa.caml/browse_frm/thread/
>> cdd54b032895c17f/9af1209426f60400#9af1209426f60400>
>> ------------------------------------------------------------------------
>> ** Xavier Leroy said:
>> 
>> Among the 150 messages that accumulated while I was at the POPL
>> conference, I notice that the topic of native-code exception
>> backtraces is making its come-back:
>> > Well, seeing that the very useful native exception backtrace patch
>> has
>> > been
>> > sitting idle (acknowledged) for more than a year, I think that's not
>> > working it out too well :\
>> 
>> Like elephants, I'm slow, but never forget :-)  You'll be pleased to
>> learn that I've been working recently on exception backtraces for
>> ocamlopt.  The code (nearly finished) currently sits in the
>> "opt_backtrace" branch of the repository and should be part of
>> release 3.10.
>> It implements an exception backtrace mechanism similar to that already
>> available in bytecode, but different from Markus Mottl's call backtrace.
>> The two kinds of backtraces are incomparable in general, but while
>> Markus's solution is quite low overhead already, mine has even lower
>> overhead, especially in terms of code size.
>> 
>> Native-code backtraces will be available initially for the following
>> back-ends: i386, amd64 and powerpc, both for Unix-like OS and for
>> Windows.  Ports to other back-ends will be considered if there is
>> sufficient demand.


--
Ingo Bormuth, voicebox & fax: +49-(0)-12125-10226517
public key 86326EC9, http://ibormuth.efil.de/contact