pthreads on FreeBSD

[Neil Long]

Hi

I do not know if it is at all relevant but a thread (!) just started 
on the freebsd-stable mail list

From:    Roman Shterenzon <roman at harmonic.co.il>
Date:    Fri Sep 29, 10:21am +0200
Subject: pthreads bug?

which indicates that there is a problem on 4.* and the attached test 
code demonstrates it. It may also be a problem on other versions.

Just in case anyone is knocking themselves out over an inherent bug 
which argus may just be triggering.

regards
Neil

The original posting is

I noticed some strange behavior in pthreads applications,
close on socket which is in accept() will be blocked untill there's a connection
to port and accept returns.
It's observed on 4.0 - 4.1-STABLE, perhaps 4.1.1-STABLE as well, but I didn't 
try it. I don't have 3.5.1-STABLE system to test it there.
It affects, for example, openldap - start it , then kill -15 it.
It won't die (and it should). Now, try to telnet localhost 389 ; now it died.
The same behavior is a program we're writing right now, it's very annoying, in
fact we don't know how to deal with it. It works on solaris and linux.
btw, linux doesn't dump core on threaded application, how one's supposed to
debug it?
I attach example program, which, when receives SIGUSR1 should close the socket,
but, in fact gets blocked in the close() function.
Obviously it's waiting to acquire some lock.
Does anyone have an idea?

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Dr Neil J Long, Computing Services, University of Oxford
 13 Banbury Road, Oxford, OX2 6NN, UK Tel:+44 1865 273232 Fax:+44 1865 273275
 EMail:       Neil.Long at computing-services.oxford.ac.uk  
 PGP:    ID 0xE88EF71F    OxCERT: oxcert at ox.ac.uk PGP: ID 0x4B11561D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pthreadtest.c
Type: application/octet-stream
Size: 1447 bytes
Desc: Data
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20000929/cc7bc09e/attachment.obj>