caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Chet Murthy <murthy.chet@gmail.com>
To: caml-list@inria.fr
Cc: Francois Berenger <berenger@riken.jp>
Subject: Re: [Caml-list] try...finally , threads, stack-tracebacks .... in ocaml
Date: Thu, 11 Apr 2013 00:17:51 -0700	[thread overview]
Message-ID: <7081577.fIKGGDAHpX@groupon> (raw)
In-Reply-To: <51666227.2040401@riken.jp>


> Isn't there a way to "trace" locking and unlocking of locks?
> 
> So that you can do a post-mortem analysis of what went wrong.

Sure.  But you'd need more locks to manage that, yes?  And
furthermore, the problem (in the case I was debugging, and many times
in my times debugging java apps) is that somebody -didn't- put locking
in plcae (e.g., java.util.NumberFormat isn't thread-safe, and yet
people will create static instances and use 'em from multiple threads,
yielding "interesting" results).

But really that's immaterial.  You can't use tracing to find
timing-related issues, b/c the trace changes the timing.

> What is the ZAM?

Sorry, the original name for the Ocaml VM was the Zinc Abstract
Machine (from Xavier's original paper).

--chet--


  reply	other threads:[~2013-04-11  7:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10 22:16 Chet Murthy
2013-04-10 22:28 ` simon cruanes
2013-04-11  0:19   ` Francois Berenger
2013-04-10 23:35 ` Yaron Minsky
2013-04-10 23:37   ` Yaron Minsky
2013-04-11  6:36     ` Malcolm Matalka
2013-04-11  6:42       ` Chet Murthy
2013-04-11  7:11         ` Francois Berenger
2013-04-11  7:17           ` Chet Murthy [this message]
2013-04-11  8:04             ` Roberto Di Cosmo
2013-04-11  8:48         ` Malcolm Matalka
2013-04-11 16:43           ` Chet Murthy
2013-04-11 11:13         ` Thomas Gazagnaire
2013-04-11  6:25 ` Jacques-Henri Jourdan

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=7081577.fIKGGDAHpX@groupon \
    --to=murthy.chet@gmail.com \
    --cc=berenger@riken.jp \
    --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).