Re: blocking socket is nonblocking after calling gnulib select() in windows

2011-04-20 Thread Ray Satiro
> On Wed, Apr 20, 2011 at 7:17 PM, Bastien ROUCARIES > wrote: > >> Is the gnulib select() only intended to be used with nonblocking sockets on > >> windows? > > > > I have just tested the program at the end of the file, it thread is > > blocked when enable =0 (block socket) and enable=1 it fa

Re: blocking socket is nonblocking after calling gnulib select() in windows

2011-04-20 Thread Bastien ROUCARIES
>> Spawning a process just to learn if a socket is blocking?  Wow. >> >> Sounds like caching the information independently (like we already do >> for dirfd) is the way to go then, so that we only have to spawn when >> inheriting sockets through stdin/out/err. > > > That is the idea But at least

Re: blocking socket is nonblocking after calling gnulib select() in windows

2011-04-20 Thread Bastien ROUCARIES
On Wed, Apr 20, 2011 at 11:53 PM, Eric Blake wrote: > On 04/20/2011 03:46 PM, Bastien ROUCARIES wrote: >> On Wed, Apr 20, 2011 at 7:17 PM, Bastien ROUCARIES >> wrote: Is the gnulib select() only intended to be used with nonblocking sockets on windows? >>> >>> I have just tested the prog

Re: blocking socket is nonblocking after calling gnulib select() in windows

2011-04-20 Thread Eric Blake
On 04/20/2011 03:46 PM, Bastien ROUCARIES wrote: > On Wed, Apr 20, 2011 at 7:17 PM, Bastien ROUCARIES > wrote: >>> Is the gnulib select() only intended to be used with nonblocking sockets on >>> windows? >> >> I have just tested the program at the end of the file, it thread is >> blocked when enab

Re: blocking socket is nonblocking after calling gnulib select() in windows

2011-04-20 Thread Bastien ROUCARIES
On Wed, Apr 20, 2011 at 7:17 PM, Bastien ROUCARIES wrote: >> Is the gnulib select() only intended to be used with nonblocking sockets on >> windows? > > I have just tested the program at the end of the file, it thread is > blocked when enable =0 (block socket) and enable=1 it fail with > WSAEWOULD

Re: blocking socket is nonblocking after calling gnulib select() in windows

2011-04-20 Thread Bastien ROUCARIES
> Is the gnulib select() only intended to be used with nonblocking sockets on > windows? I have just tested the program at the end of the file, it thread is blocked when enable =0 (block socket) and enable=1 it fail with WSAEWOULDBLOCK So i possible stragegy will be: 1. createathread TID from par

[PATCH] useless-if-before-free: avoid false-positive

2011-04-20 Thread Jim Meyering
FYI, while fixing gcc's useless-if-before-free, I learned of this bug: From 67ce653056298965788199437efe1e0f6c06eec5 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Wed, 20 Apr 2011 15:44:54 +0200 Subject: [PATCH] useless-if-before-free: avoid false-positive * build-aux/useless-if-before-free:

Re: [PATCH] doc: update users.txt.

2011-04-20 Thread Jim Meyering
Giuseppe Scrivano wrote: > Another gnulib "victim". ... > Subject: [PATCH] doc: update users.txt. ... > + barcode http://savannah.gnu.org/projects/barcode/ Thanks. I've pushed that after adjusting the URL to be the cgit one rather than the project one, to be consistent with most of the o