caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Ingo Bormuth <ibormuth@efil.de>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Exception backtraces
Date: Wed, 24 Jan 2007 22:53:29 +0100	[thread overview]
Message-ID: <20070124215329.GA31041@efil.de> (raw)
In-Reply-To: <6dbd4d000701221854v1fa172a9k59c0023e382fb2a7@mail.gmail.com>

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


  reply	other threads:[~2007-01-24 21:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23  2:54 Denis Bueno
2007-01-24 21:53 ` Ingo Bormuth [this message]
2007-01-25  2:32   ` [Caml-list] " Denis Bueno
2007-01-25  2:47     ` Jon Harrop
2007-01-25  4:57       ` Denis Bueno
2007-01-25 22:37       ` Jan Rehders
2007-01-25  3:31     ` Erik de Castro Lopo

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=20070124215329.GA31041@efil.de \
    --to=ibormuth@efil.de \
    --cc=caml-list@yquem.inria.fr \
    /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;
as well as URLs for NNTP newsgroup(s).