Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Feb 2004 10:26:42 -0600
From:      Jeremy Messenger <mezz7@cox.net>
To:        Khairil Yusof <kaeru@pd.jaring.my>
Cc:        Hye-Shik Chang <perky@i18n.org>
Subject:   Re: Need the help on debug the Python VS libpthread..
Message-ID:  <opr3vumsks8ckrg5@smtp.central.cox.net>
In-Reply-To: <1077615520.1002.10.camel@wolverine.cerebro.net.my>
References:  <opr3olwhti8ckrg5@smtp.central.cox.net> <20040224091827.GA9742@i18n.org> <1077615520.1002.10.camel@wolverine.cerebro.net.my>

next in thread | previous in thread | raw e-mail | index | archive | help
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. :-)

Cheers,
Mezz

On Tue, 24 Feb 2004 17:38:41 +0800, Khairil Yusof <kaeru@pd.jaring.my> 
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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?opr3vumsks8ckrg5>