From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id XAA12157 for caml-red; Wed, 5 Jul 2000 23:15:54 +0200 (MET DST) Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id XAA10992 for ; Mon, 3 Jul 2000 23:44:10 +0200 (MET DST) Received: from wally.eecs.harvard.edu (wally.eecs.harvard.edu [140.247.60.30]) by nez-perce.inria.fr (8.10.0/8.10.0) with ESMTP id e63Li9519933 for ; Mon, 3 Jul 2000 23:44:09 +0200 (MET DST) Received: from labrador.eecs.harvard.edu (labrador.eecs.harvard.edu [140.247.60.247]) by wally.eecs.harvard.edu (8.10.0/8.10.0) with ESMTP id e63Lhrd20923 for ; Mon, 3 Jul 2000 17:43:53 -0400 (EDT) Message-Id: <200007032143.e63Lhrd20923@wally.eecs.harvard.edu> To: caml-list@inria.fr Subject: Re: how to set breakpoint at exception throw? In-Reply-To: Message from Patrick M Doane of "Mon, 03 Jul 2000 11:05:55 EDT." Date: Mon, 03 Jul 2000 17:43:53 -0400 From: Norman Ramsey Sender: weis@pauillac.inria.fr Let me add my voice to the crowd: if the default behavior of a failing caml program were to produce a trace of uncaught exceptions, my life would be easier. It will be especially helpful when we start shipping buggy caml programs to unsuspecting users, who can't reasonably be asked to run the caml debugger... Norman