From owner-freebsd-python@FreeBSD.ORG  Tue Feb 24 16:42:47 2004
Return-Path: <owner-freebsd-python@FreeBSD.ORG>
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 718E316A4CE
	for <python@freebsd.org>; Tue, 24 Feb 2004 16:42:47 -0800 (PST)
Received: from miffy.openlook.org (openlook.org [211.236.182.73])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 037AF43D1D
	for <python@freebsd.org>; Tue, 24 Feb 2004 16:42:47 -0800 (PST)
	(envelope-from perky@miffy.openlook.org)
Received: by miffy.openlook.org (Postfix, from userid 1000)
	id A915DA9C1; Wed, 25 Feb 2004 09:46:25 +0900 (KST)
Date: Wed, 25 Feb 2004 09:46:25 +0900
From: Hye-Shik Chang <perky@i18n.org>
To: Daniel Eischen <eischen@vigrid.com>
Message-ID: <20040225004625.GA20828@i18n.org>
References: <opr3v3z30q8ckrg5@smtp.central.cox.net>
	<Pine.GSO.4.10.10402241722080.3438-100000@pcnet5.pcnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.10.10402241722080.3438-100000@pcnet5.pcnet.com>
X-Accept-Language: ko, en
User-Agent: Mutt/1.5.5.1i
cc: Jeremy Messenger <mezz7@cox.net>
cc: Julian Elischer <julian@elischer.org>
cc: python@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 <freebsd-python.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>,
	<mailto:freebsd-python-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python>
List-Post: <mailto:freebsd-python@freebsd.org>
List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>,
	<mailto:freebsd-python-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2004 00:42:47 -0000

On Tue, Feb 24, 2004 at 05:26:13PM -0500, Daniel Eischen wrote:
> On Tue, 24 Feb 2004, Jeremy Messenger wrote:
> 
> > 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.
> 
> It is not necessarily a problem with libpthread.  waitpid() can
> return EINTR when interrupted by a signal.  If SIGCHLD isn't
> masked by the thread, then it is certainly plausible that it
> can get interrupted by it.
> 
> You may not have seen it with libc_r because it handles signals
> differently as well as wrap waitpid() so it doesn't block the
> process.  Libpthread doesn't wrap waitpid() except to make it
> a cancellation point.  If its returning EINTR, I would suspect
> that it has received a signal.

I see. Thanks for the kind explanation and sorry for my confusing. :)

The fix is checked in Python CVS.
http://mail.python.org/pipermail/python-checkins/2004-February/039939.html


Thanks,
Hye-Shik