Need the help on debug the Python VS libpthread..

[Hye-Shik Chang]

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