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 nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by yquem.inria.fr (Postfix) with ESMTP id 0F8AEBB9A for ; Mon, 14 Nov 2005 10:49:33 +0100 (CET) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id jAE9nWqE003621 for ; Mon, 14 Nov 2005 10:49:32 +0100 Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id KAA16424 for ; Mon, 14 Nov 2005 10:49:32 +0100 (MET) Received: from furbychan.cocan.org (furbychan.cocan.org [80.68.91.176]) by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id jAE9nSrZ010518 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 14 Nov 2005 10:49:31 +0100 Received: from rich by furbychan.cocan.org with local (Exim 3.35 #1 (Debian)) id 1EbbHV-0005p2-00; Mon, 14 Nov 2005 10:09:45 +0000 Date: Mon, 14 Nov 2005 10:09:45 +0000 To: xuzq Cc: caml-list@inria.fr Subject: Re: [Caml-list] perl4caml crashed with threads Message-ID: <20051114100945.GA20179@furbychan.cocan.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i From: Richard Jones X-Miltered: at nez-perce with ID 43785DAC.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Miltered: at concorde with ID 43785DA8.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; caml-list:01 threads:01 bug:01 threads:01 thread-safe:01 notepad:01 wrote:01 caml:02 caml:02 debian:02 dump:03 crashes:04 crashed:04 marketing:93 core:06 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.3 On Mon, Nov 14, 2005 at 02:16:43AM +0000, xuzq wrote: > On my debian sid box,the following prog core dump.What's wrong?Is it > all right on your machine or is it a bug? This crashes on my machine too. However if you remove all references to threads, then it works. libperl and perl4caml don't make any attempt to be thread-safe. Rich. -- Richard Jones, CTO Merjis Ltd. Merjis - web marketing and technology - http://merjis.com Team Notepad - intranets and extranets for business - http://team-notepad.com