caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yaron Minsky <yminsky@gmail.com>
To: Caml Mailing List <caml-list@inria.fr>
Subject: Why are backtraces (sometimes) useless
Date: Fri, 24 Jun 2005 12:39:24 -0400	[thread overview]
Message-ID: <891bd339050624093978a3c9a8@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 789 bytes --]

I've had a lot of experience lately with OCaml backtraces sucking, and I'm 
not sure what's going on. We're working on a decent-sizes project (about 
10-kloc) that uses threads and a decent amount of functorization. One thing 
we've noticed is that backtraces are almost completely useless --- generally 
speaking, they have lots of "Called from unknown location" messages, and 
almost no useful data. They often skip over functions on the call stack of 
the error in surprising ways.

I guess the question is this: what kind of situations cause backtraces to 
drop information in the ways described above?

Also, is there anyone out there actively using the native-code backtrace 
patches that people have come up with? I'm curious to hear other people's 
experiences.

y

[-- Attachment #2: Type: text/html, Size: 854 bytes --]

             reply	other threads:[~2005-06-24 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 16:39 Yaron Minsky [this message]
2005-06-24 16:54 ` [Caml-list] " malc
2005-06-24 18:32 ` Richard Jones

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=891bd339050624093978a3c9a8@mail.gmail.com \
    --to=yminsky@gmail.com \
    --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).