From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id 91EFFBC57 for ; Wed, 8 Sep 2010 09:51:41 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArEEAEPdhkxQW+UMgWdsb2JhbACTYI0tFgEWIiK+OoU9BIhugSk X-IronPort-AV: E=Sophos;i="4.56,333,1280700000"; d="scan'208";a="69043517" Received: from lo.gmane.org ([80.91.229.12]) by mail4-smtp-sop.national.inria.fr with ESMTP; 08 Sep 2010 09:51:41 +0200 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OtFRT-0000uq-WC for caml-list@inria.fr; Wed, 08 Sep 2010 09:51:40 +0200 Received: from ks368928.kimsufi.com ([94.23.39.26]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 08 Sep 2010 09:51:39 +0200 Received: from sylvain by ks368928.kimsufi.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 08 Sep 2010 09:51:39 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: caml-list@inria.fr From: Sylvain Le Gall Subject: Re: Possible ocamlmpi finalization error? Date: Wed, 8 Sep 2010 07:51:31 +0000 (UTC) Message-ID: References: X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: ks368928.kimsufi.com User-Agent: slrn/pre1.0.0-11 (Linux) X-Spam: no; 0.00; le-gall:01 ocamlmpi:01 eray:01 ozkural:01 ocamlmpi:01 bug:01 goodbye:98 wrote:01 finalization:01 reproduce:03 library:03 mpi:04 mpi:04 finalize:05 correct:08 On 08-09-2010, Eray Ozkural wrote: > --===============0522474025== > Content-Type: multipart/alternative; boundary=0016369204e79d9601048fb8ae36 > > --0016369204e79d9601048fb8ae36 > Content-Type: text/plain; charset=ISO-8859-1 > > I'm recently getting errors that are past MPI_Finalize. Since both > init/final and communicator allocation is managed by ocamlmpi, is it > possible this is a bug with the library? Have you ever seen something like > this? > > Using openmpi on OS X. Here is the log message: > > *** An error occurred in MPI_Comm_free > *** after MPI was finalized > *** MPI_ERRORS_ARE_FATAL (goodbye) > > In the code I'm using both point-to-point and collective communication, and > as far as I know the code is correct. Could this be due to memory > corruption, or should this never happen? > Maybe, you can give a minimal code to reproduce this error? Regards, Sylvain Le Gall