Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 28 Jan 1999 08:16:40 -0600
From:      "Richard Seaman, Jr." <dick@tar.com>
To:        "Sergey S. Kosyakov" <ks@itp.ac.ru>
Cc:        freebsd-hackers@FreeBSD.ORG
Subject:   Re: select(2) and threads
Message-ID:  <19990128081640.Q421@tar.com>
In-Reply-To: <XFMail.990128170418.ks@itp.ac.ru>; from Sergey S. Kosyakov on Thu, Jan 28, 1999 at 05:04:18PM %2B0300
References:  <XFMail.990128170418.ks@itp.ac.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 28, 1999 at 05:04:18PM +0300, Sergey S. Kosyakov wrote:

> it seems that calling select in more than one concurrent thread cause all such
> threads except the last to block forever. The same situation is with poll(). The
> only case when select() and poll() work is when timeout is set to 0.
> Is select really thread safe in FreeBSD?

What compile/link flags are you using?  The poll function isn't implemented
for libc_r, AFAIK (I'm assuming you're using the libc_r "user thread" code
right?).

If you're able to use poll, chances are good you've linked against libc, so
you're probably geting the libc select, and not the libc_r select.  This
would account for the symptoms you describe.

-- 
Richard Seaman, Jr.           email: dick@tar.com
5182 N. Maple Lane            phone: 414-367-5450
Chenequa WI 53058             fax:   414-367-5852

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



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