caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Denis Bueno" <dbueno@gmail.com>
To: "Ingo Bormuth" <ibormuth@efil.de>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Exception backtraces
Date: Wed, 24 Jan 2007 21:32:55 -0500	[thread overview]
Message-ID: <6dbd4d000701241832n40cfd1b8p40fa2300699e086d@mail.gmail.com> (raw)
In-Reply-To: <20070124215329.GA31041@efil.de>

On 1/24/07, Ingo Bormuth <ibormuth@efil.de> wrote:
> 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:
[snip long post]

I did see that, but, since I'm compiling into bytecode (which,
granted, I did not specify), I didn't think it applied to me. In any
event, it doesn't specify how exactly to *get* backtraces (apart from
OCAMLPARAM="b") at all.

Is there a way?

-Denis


  reply	other threads:[~2007-01-25  2:32 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 ` [Caml-list] " Ingo Bormuth
2007-01-25  2:32   ` Denis Bueno [this message]
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=6dbd4d000701241832n40cfd1b8p40fa2300699e086d@mail.gmail.com \
    --to=dbueno@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=ibormuth@efil.de \
    /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).