From owner-freebsd-python@FreeBSD.ORG Tue Feb 24 11:50:12 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47A1416A4CE; Tue, 24 Feb 2004 11:50:12 -0800 (PST) Received: from lakemtao06.cox.net (lakemtao06.cox.net [68.1.17.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id A673F43D39; Tue, 24 Feb 2004 11:50:11 -0800 (PST) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.11]) by lakemtao06.cox.net (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with ESMTP id <20040224195011.SUDZ3458.lakemtao06.cox.net@mezz.mezzweb.com>; Tue, 24 Feb 2004 14:50:11 -0500 Date: Tue, 24 Feb 2004 13:49:05 -0600 To: Julian Elischer References: From: Jeremy Messenger Content-Type: text/plain; format=flowed; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: User-Agent: Opera7.23/Linux M2 build 518 cc: Hye-Shik Chang cc: python@FreeBSD.org cc: Khairil Yusof cc: freebsd-threads@freebsd.org Subject: Re: Need the help on debug the Python VS libpthread.. X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 19:50:12 -0000 On Tue, 24 Feb 2004 10:57:32 -0800 (PST), Julian Elischer wrote: > > > On Tue, 24 Feb 2004, Jeremy Messenger wrote: > >> Great, thank guys! I now can install net/straw with optimized on >> libpthread. I am adding -thread in the CC, so the thread developers can >> catch here too. :-) > > so what was fixed between teh quoted mail below and now? A workaround (not real fix?) as perky has committed[1]. There's something wrong with waitpid if it runs as libpthread, since without the workaround can run fine with libc_r. [1] http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/python/files/patch-Lib%3a%3adistutils%3a%3aspawn.py Cheers, Mezz >> Cheers, >> Mezz >> >> On Tue, 24 Feb 2004 17:38:41 +0800, Khairil Yusof >> wrote: >> >> > On Tue, 2004-02-24 at 18:18 +0900, Hye-Shik Chang wrote: >> > >> >> I am not sure if it's Python problem or our libpthread problem. I >> >> failed to reproduce the situation with compact C code. (waitpid(2) >> >> returned -1 with errno=EINTR on a child's normal termination.) >> >> If you get a reasonable explanation that saying it's Python's >> >> problem, please tell me. >> > >> > Great, thanks for the info. I can duplicate this problem with mail/ >> > evolution also. >> > >> > It may be a more universal problem caused by libpthread. At least it >> > also effects evolution1.5's em-junk-filter.c and other shell calls >> that >> > use waitpid. evolution doesn't catch it either, resulting in a hanged >> > process loop that has to be killed (also under libpthread). >> > >> > -- >> > "You keep using that word. I do not think it means what you think it >> > means." >> > >> > FreeBSD 5.2-CURRENT i386 >> > 5:26pm up 1:05, 1 user, load averages: 0.58, 0.40, 0.42 -- bsdforums.org 's moderator, mezz.