From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Delivered-To: caml-list@yquem.inria.fr Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by yquem.inria.fr (Postfix) with ESMTP id 38799BCAE for ; Tue, 12 Jul 2005 19:10:54 +0200 (CEST) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id j6CHAr4s003378 for ; Tue, 12 Jul 2005 19:10:54 +0200 Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id TAA04234 for ; Tue, 12 Jul 2005 19:10:53 +0200 (MET DST) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by nez-perce.inria.fr (8.13.0/8.13.0) with SMTP id j6CHArrb025927 for ; Tue, 12 Jul 2005 19:10:53 +0200 Received: (qmail 18201 invoked by uid 0); 12 Jul 2005 17:10:52 -0000 Received: from 212.122.56.2 by www83.gmx.net with HTTP; Tue, 12 Jul 2005 19:10:52 +0200 (MEST) Date: Tue, 12 Jul 2005 19:10:52 +0200 (MEST) From: "Sebastian Wendt" To: caml-list@inria.fr MIME-Version: 1.0 Subject: =?ISO-8859-1?Q?Mutex.lock_error_code_0?= X-Priority: 3 (Normal) X-Authenticated: #171994 Message-ID: <21118.1121188252@www83.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Miltered: at concorde with ID 42D3F99D.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Miltered: at nez-perce with ID 42D3F99D.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; threads:01 iterating:01 threads:01 protects:98 workaround:01 thread:02 seems:03 terribly:03 sys:03 mutex:03 mutex:03 clue:04 elements:05 stupid:09 object:09 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on yquem.inria.fr X-Spam-Status: No, score=0.1 required=5.0 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.2 X-Spam-Level: Recently I keep receiving those "Mutex.lock: error code 0" error messages as a Sys_error ( using system threads under Win32 ) The mutex protects a list, both inside an object, together with a thread iterating over this list. There is a method which allows other threads to add elements to the list, locking the mutex before accessing the list. Nothing special at all. The error seems so terribly stupid to me that I have no clue where to start looking for a workaround. If you could provide me with any information about the reason / documentation or where to find it, I would be greatly thankful. Thanks Sebastian -- 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail +++ GMX - die erste Adresse für Mail, Message, More +++