From: Richard Jones <rich@annexia.org>
To: "Yaron M. Minsky" <yminsky@cs.cornell.edu>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] getting stack traces in running code
Date: Tue, 2 Dec 2003 21:45:13 +0000 [thread overview]
Message-ID: <20031202214513.GA21019@redhat.com> (raw)
In-Reply-To: <1070398239.15748.57.camel@flapdragon.homeip.net>
On Tue, Dec 02, 2003 at 03:50:40PM -0500, Yaron M. Minsky wrote:
> Is there a reason why stack traces are available only on a crash? I
> have a project (a distributed OpenPGP keyserver system,
> http://www.nongnu.org/sks/) that is a long-running daemon. Unexpected
> errors are caught and logged, but unfortunately, there's no way of
> getting a stack-trace, since I don't let the exceptions kill the
> program. This makes debugging much more difficult, and is one of the
> single largest difficulties I have with ocaml. Is there a technical
> reason that a bytecode-compiled executable couldn't have access to the
> stack trace during execution?
Us too.
A backtrace facility for exceptions would be enormously useful.
Rich.
--
Richard Jones. http://www.annexia.org/ http://freshmeat.net/users/rwmj
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
"One serious obstacle to the adoption of good programming languages is
the notion that everything has to be sacrificed for speed. In computer
languages as in life, speed kills." -- Mike Vanier
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-12-02 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 20:50 Yaron M. Minsky
2003-12-02 21:45 ` Richard Jones [this message]
2003-12-02 22:26 ` Issac Trotts
2003-12-03 3:19 ` Nicolas Cannasse
2003-12-03 14:19 ` Damien Doligez
2003-12-03 18:26 ` Issac Trotts
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=20031202214513.GA21019@redhat.com \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=yminsky@cs.cornell.edu \
/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).