Re: [Chicken-users] `tcp-connect' permanently blocks if connecting to a non-existing port

[Goetz Isenmann]

On Wed, Aug 23, 2006 at 11:04:39PM +0200, felix winkelmann wrote:
> On 8/23/06, Dmitry Lizorkin <address@hidden> wrote:
> >Hello,
> >In the following piece of code
> >
> >(require-extension tcp)
> >(tcp-connect "localhost" 5050)
> >
> >`tcp-connect' permanently blocks if nobody is listening to the 
> >corresponding
> >port. We observed this for Chicken 2.41 for both Linux and Windows & for
> >both local and remote connections.
> >
> 
> It should give an error. Very strange. Do other threads still run?

I think that (only) on windows I did not get a timeout error for an
async connect.

If I remember correctly, I was setting a socket nonblocking, did a
connect, and then was waiting in select forever. The socket was never
(many minutes) signaled as writable.

Not sure, if this is relevant here...
-- 
Goetz Isenmann