Need the help on debug the Python VS libpthread..

[Jeremy Messenger]

On Tue, 24 Feb 2004 10:57:32 -0800 (PST), Julian Elischer 
<julian at elischer.org> 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 <kaeru at 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.