From: "Yaron M. Minsky" <yminsky@cs.cornell.edu>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] getting stack traces in running code
Date: Tue, 02 Dec 2003 15:50:40 -0500 [thread overview]
Message-ID: <1070398239.15748.57.camel@flapdragon.homeip.net> (raw)
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?
y
--
|--------/ Yaron M. Minsky \--------|
|--------\ http://www.cs.cornell.edu/home/yminsky/ /--------|
Open PGP --- KeyID B1FFD916
Fingerprint: 5BF6 83E1 0CE3 1043 95D8 F8D5 9F12 B3A9 B1FF D916
-------------------
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 reply other threads:[~2003-12-02 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 20:50 Yaron M. Minsky [this message]
2003-12-02 21:45 ` Richard Jones
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=1070398239.15748.57.camel@flapdragon.homeip.net \
--to=yminsky@cs.cornell.edu \
--cc=caml-list@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).