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=1.1 required=5.0 tests=AWL,SPF_NEUTRAL 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 6D6BEBC69 for ; Wed, 1 Aug 2007 23:10:43 +0200 (CEST) Received: from lepore.amnh.org (lepore.amnh.org [216.73.241.12]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id l71LAgms023776 for ; Wed, 1 Aug 2007 23:10:43 +0200 Received: from localhost (localhost [127.0.0.1]) by lepore.amnh.org (Postfix) with ESMTP id B7F035B76A for ; Wed, 1 Aug 2007 17:10:41 -0400 (EDT) X-Virus-Scanned: amavisd-new at amnh.org Received: from lepore.amnh.org ([127.0.0.1]) by localhost (lepore.amnh.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OTPXz2xnNda8 for ; Wed, 1 Aug 2007 17:10:39 -0400 (EDT) Received: from [172.16.63.190] (216-73-250-179.dynamic.amnh.org [216.73.250.179]) by lepore.amnh.org (Postfix) with ESMTP id DC92E5B768 for ; Wed, 1 Aug 2007 17:10:39 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <7209A0C0-93DC-46A9-940D-47C54EB31E1B@gmail.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: OCaml List From: Andres Varon Subject: segfault in 3.10.0 Date: Wed, 1 Aug 2007 17:10:38 -0400 X-Mailer: Apple Mail (2.752.3) X-j-chkmail-Score: MSGID : 46B0F6D2.001 on discorde : j-chkmail score : X : 0/20 1 0.000 -> 1 X-Miltered: at discorde with ID 46B0F6D2.001 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; segfault:01 segfaults:01 ocaml:01 segfault:01 camlp:01 inputs:01 segfaults:01 ocaml:01 pointer:01 nightly:98 compile:01 delayed:01 structures:02 structures:02 unit:03 Hello Everyone, Has anyone observed sudden segfaults in OCaml 3.10.0 amd-64 under linux? I have this program that has been run for quite a while without any segfault (almost a year). It may run for weeks at a time in parallel in our cluster, using as many as 256 processors at a time. We delayed updating to 3.10.0 due to the changes in camlp4, but the day before yesterday I worked on it, upgraded, and suddenly a lot of the nightly unit tests in 64 bits fail with a segfault (a LOT of them), when every test passed clean with 3.09.3. None of the tests for other architectures fail though (windows, mac os X intel and 32- bit ppc). One down side is that we have C structures wrapped, so one may blame our program. However, efence and valgrind show no sign of problem, and the fact that we have been using those structures for a while, and many test iterations have passed for many inputs, and not only us, but many people in other computers have compiled and run our program without having segfaults ... I'm doubtful. Unfortunately I have been unable to compile 3.10.0 for 64 bits in our g5 under Mac OS X, so that architecture remains untested. The segfault is occurring within the OCaml code. Any pointer would be greatly appreciated, or suggestions of tools that could help us hunting this down ... I'm awfully clueless about what to do today ... and it's been just a couple of days :-( best, Andres