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=AWL autolearn=disabled version=3.1.3 Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by yquem.inria.fr (Postfix) with ESMTP id F0195BB84 for ; Tue, 3 Jun 2008 16:08:48 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqMAADXtREjBL1AZomdsb2JhbACSBAEBAQEBCAUGCRGdQA X-IronPort-AV: E=Sophos;i="4.27,583,1204498800"; d="scan'208";a="13156007" Received: from gw.exalead.com (HELO exalead.com) ([193.47.80.25]) by mail1-smtp-roc.national.inria.fr with ESMTP; 03 Jun 2008 16:08:48 +0200 Received: from [192.168.204.148] (madpc064.exalead.com [192.168.204.148]) (authenticated bits=0) by exalead.com (8.14.2/8.14.0) with ESMTP id m53E8liv012550; Tue, 3 Jun 2008 16:08:47 +0200 Message-ID: <4845506F.8000808@exalead.com> Date: Tue, 03 Jun 2008 16:08:47 +0200 From: Berke Durak User-Agent: Thunderbird 1.5.0.10 (X11/20070221) MIME-Version: 1.0 To: Jacques Le Normand Cc: caml-list@yquem.inria.fr Subject: Re: [Caml-list] Segmentation fault References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam: no; 0.00; berke:01 durak:01 berke:01 durak:01 segfault:01 ocaml:01 segfault:01 segfaults:01 ocamlc:01 ocamlopt:01 ocamldebug:01 segfaults:01 bug:01 wrote:01 caml-list:01 Jacques Le Normand wrote: > Hello caml-list, > > I'm encountering a segfault on ocaml 3.09 > > The test case seems long, but if I remove any line from it it stops > segfaulting. The strangest thing is that get_right_sibling_specific is > called, though it appears nowhere. If you change it's name, the segfault > dissapears. Any help would be appreciated! > here's the code: I confirm that it segfaults with ocamlc and ocamlopt 3.11+dev12 on amd64. Stepping with ocamldebug, I find that it segfaults somewhere near this: Time : 3045 - pc : 58100 - module CamlinternalOO 323 if top then super cla env else <|b|>Obj.repr (super cla) in So this indeed looks like a bug in the object system. -- Berke DURAK