Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#587 socket-connect with timeout non-zero ->ETIMEDOUT

lisp error
closed-fixed
Sam Steingold
clisp (525)
5
2011-03-28
2011-02-15
Don Cohen
No

> > [5]> (multiple-value-setq (socket err) (ignore-errors
> > (SOCKET:SOCKET-CONNECT 80
> > "localhost" :timeout 1 :element-type '(unsigned-byte 8))))
> >
> > [../src/stream.d:14257] NIL
> > [6]> (format nil "~a" err)
> > "UNIX error 110 (ETIMEDOUT): Connection timed out
> > "
...
> indeed this is a regression over 2.44.1.
> could you please try to pin down which version caused this behavior and
> file a bug report on SF?
> thanks.

Earliest I can find so far already on my machines after 2.44 is
2.47+ as of 2008-10-24 and that has the bug.

Discussion

  • Sam Steingold
    Sam Steingold
    2011-03-28

    The first bad revision is:
    changeset: 12825:6a6b67512ef8
    user: sds
    date: Mon Jun 30 19:33:01 2008 +0000
    summary: fix bug #[ 2007052 ] socket-connect with :timeout to a dead port

     
  • Sam Steingold
    Sam Steingold
    2011-03-28

    thank you for your bug report.
    the bug has been fixed in the source tree (mercurial/hg).
    you can either wait for the next release (recommended)
    or check out the current mercurial tree (see http://clisp.org\)
    and build CLISP from the sources (be advised that between
    releases the source tree is very unstable and may not even build
    on your platform).

     
  • Sam Steingold
    Sam Steingold
    2011-03-28

    • assigned_to: haible --> sds
    • status: open --> closed-fixed