Re: Strange select(2) misbehaviour when linked with -pthread

2001-07-27 Thread David Malone
On Thu, Jul 26, 2001 at 02:56:08PM +0300, Maxim Sobolev wrote: > I am not sure that the error is what we want to get in this situation. > Perhaps more *compatible* solution would be wait indefinitely if timeout > is too large. I guess this could cause problems for programs that use select to time

Re: Strange select(2) misbehaviour when linked with -pthread

2001-07-26 Thread Warner Losh
In message <[EMAIL PROTECTED]> David Malone writes: : Or don't work as the case may be ;-) Posix doesn't actually require : select to be able to deal with large wait times (I think 31 days was : the figure I found in the SUSv2 spec). Have a look at: 31 days, interestingly enough, is very close to

Re: Strange select(2) misbehaviour when linked with -pthread

2001-07-26 Thread Maxim Sobolev
> > On Wed, Jul 25, 2001 at 02:12:06PM +0300, Maxim Sobolev wrote: > > I found that the attached small program behaves very strangely when > > linked with -pthread - it chews 100% CPU cycles while waiting in > > select(2). This misbehaviour observed both on 5-CURRENT and 4-STABLE > > systems. *we

Re: Strange select(2) misbehaviour when linked with -pthread

2001-07-26 Thread David Malone
On Wed, Jul 25, 2001 at 02:12:06PM +0300, Maxim Sobolev wrote: > I found that the attached small program behaves very strangely when > linked with -pthread - it chews 100% CPU cycles while waiting in > select(2). This misbehaviour observed both on 5-CURRENT and 4-STABLE > systems. *weird* The tim