From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Ohad Rodeh <orodeh@cs.huji.ac.il>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] exception tracing with Threads
Date: Fri, 6 Apr 2001 17:47:21 +0200 [thread overview]
Message-ID: <20010406174721.C3481@pauillac.inria.fr> (raw)
In-Reply-To: <Pine.LNX.4.20_heb2.08.0104051553030.23901-100000@zigzag.cs.huji.ac.il>; from orodeh@cs.huji.ac.il on Thu, Apr 05, 2001 at 03:55:53PM +0200
> I've just tried to use the exception tracing
> mechanism for threads. Unfortunately, when using
> threads this option is not enabled.
Right. That's an oversight. I agree it would be useful to have a
stack backtrace for threads that terminate on an exception. It's not
absolutely trivial to implement, though. I push this on my to do stack.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
prev parent reply other threads:[~2001-04-06 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 13:55 Ohad Rodeh
2001-04-06 15:47 ` Xavier Leroy [this message]
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=20010406174721.C3481@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=orodeh@cs.huji.ac.il \
/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).