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 XAA12976 for caml-red; Wed, 5 Jul 2000 23:31:52 +0200 (MET DST) Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id XAA28765 for ; Wed, 5 Jul 2000 23:29:53 +0200 (MET DST) Received: from mail1.microsoft.com (mail1.microsoft.com [131.107.3.125]) by concorde.inria.fr (8.10.0/8.10.0) with SMTP id e65LToX00462 for ; Wed, 5 Jul 2000 23:29:51 +0200 (MET DST) Received: from 157.54.9.101 by mail1.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 05 Jul 2000 14:29:29 -0700 (Pacific Daylight Time) Received: by INET-IMC-01 with Internet Mail Service (5.5.2651.58) id ; Wed, 5 Jul 2000 14:29:29 -0700 Message-ID: <39ADCF833E74D111A2D700805F1951EF18014753@RED-MSG-06> From: Don Syme To: "'Norman Ramsey'" , caml-list@inria.fr Subject: RE: how to set breakpoint at exception throw? Date: Wed, 5 Jul 2000 14:29:26 -0700 X-Mailer: Internet Mail Service (5.5.2651.58) Sender: weis@pauillac.inria.fr For what it's worth, some sort of indication of where execution was when a stack overflow happens would also be great. Cheers, Don -----Original Message----- From: Norman Ramsey [mailto:nr@eecs.harvard.edu] Sent: 03 July 2000 22:44 To: caml-list@inria.fr Subject: Re: how to set breakpoint at exception throw? 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