From: Jan Rehders <cmdkeen@gmx.de>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Exception backtraces
Date: Thu, 25 Jan 2007 23:37:09 +0100 [thread overview]
Message-ID: <1135D43F-2E89-4D88-B38D-D3A16933739D@gmx.de> (raw)
In-Reply-To: <200701250247.39780.jon@ffconsultancy.com>
On 25. Jan 2007, at 03:47, Jon Harrop wrote:
> On Thursday 25 January 2007 02:32, Denis Bueno wrote:
>> 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")
>
> Can you explain what you want that CAMLPARAM=b does not provide?
Is it possible to get backtraces for the toplevel? I've tried to do
it similar to the solution for the ocaml bytecode compiler but had no
luck
-- Jan R.
next prev parent reply other threads:[~2007-01-25 22:34 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
2007-01-25 2:47 ` Jon Harrop
2007-01-25 4:57 ` Denis Bueno
2007-01-25 22:37 ` Jan Rehders [this message]
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=1135D43F-2E89-4D88-B38D-D3A16933739D@gmx.de \
--to=cmdkeen@gmx.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).