From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from discorde.inria.fr (discorde.inria.fr [192.93.2.38]) by yquem.inria.fr (Postfix) with ESMTP id 4188EBC0B for ; Fri, 15 Dec 2006 11:19:02 +0100 (CET) Received: from smeltpunt.science.ru.nl (smeltpunt.science.ru.nl [131.174.16.145]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id kBFAJ1Ji025851 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 15 Dec 2006 11:19:02 +0100 Received: from tandem.cs.ru.nl [131.174.142.18] (helo=tandem.cs.ru.nl) by smeltpunt.science.ru.nl (8.13.7/5.10) with ESMTP id kBFAJ1cR014033 for ; Fri, 15 Dec 2006 11:19:01 +0100 (MET) Received: from tews by tandem.cs.ru.nl with local (Exim 4.63) (envelope-from ) id 1GvA9d-00036E-8T for caml-list@inria.fr; Fri, 15 Dec 2006 11:19:01 +0100 From: Hendrik Tews To: caml-list@inria.fr Subject: Re: [Caml-list] Caml-Debugger segmentation fault References: <17724.38598.826829.236021@tandem.cs.ru.nl> Date: Fri, 15 Dec 2006 11:19:01 +0100 In-Reply-To: <17724.38598.826829.236021@tandem.cs.ru.nl> (Hendrik Tews's message of "Mon, 23 Oct 2006 12:17:42 +0200") Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Scanned-By: MIMEDefang 2.56 on 131.174.16.145 X-Miltered: at discorde with ID 45827695.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; hendrik:01 tews:01 tews:01 hendrik:01 bool:01 ocaml-heap:01 debugger:01 bytecode:01 debugger:01 bytecode:01 writes:01 caml-list:01 data:02 segmentation:03 segmentation:03 Hendrik Tews writes: With "3.09.3+ty2" I get a Caml-Debugger segmentation fault after "print *" (on a function that returns a bool). Can this be caused by a program working on possibly corrupted ocaml-heap data? Just for the record: I used the 3.09.3 debugger on a 3.09.3+ty2 bytecode image, the 3.09.3+ty2 debugger worked fine. Maybe the debugger could check the bytecode version before segfaulting? Hendrik