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 JAA20337 for caml-redistribution; Thu, 24 Jul 1997 09:35:45 +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 JAA20310 for <caml-list@pauillac.inria.fr>; Thu, 24 Jul 1997 09:35:05 +0200 (MET DST)
Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35])
	by concorde.inria.fr (8.8.5/8.8.5) with ESMTP id JAA26170;
	Thu, 24 Jul 1997 09:35:02 +0200 (MET DST)
Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id JAA20302; Thu, 24 Jul 1997 09:35:01 +0200 (MET DST)
From: Pierre Weis <Pierre.Weis@inria.fr>
Message-Id: <199707240735.JAA20302@pauillac.inria.fr>
Subject: Re: Stack traces
In-Reply-To: <199707232133.RAA16346@kalgoorlie.cs.umass.edu> from "Adam P. Jenkins" at "Jul 23, 97 05:33:18 pm"
To: ajenkins@cs.umass.edu (Adam P. Jenkins)
Date: Thu, 24 Jul 1997 09:35:01 +0200 (MET DST)
Cc: caml-list@inria.fr
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: weis

> Hi, 
> 	Is there any way to get a stack trace, or even core dump, when
> an uncaught exception occurs in O'Caml?  Getting
>  
> 	Fatal error: out-of-bound access in array or string
> 
> isn't much more useful than the traditional segfault, and is less
> useful than a core dump; it tells me why the program crashed but not
> where.

[...]

You should have a look to the Caml debugger: it gives you a back trace
facility and backward execution as well.

Best regards,

Pierre Weis

INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://pauillac.inria.fr/~weis/