[bug] USOCKET:TIMEOUT-ERROR was signalled.

[JuanitoFatas]

OS: OSX 10.6.8 Lisp: SBCL 1.1.7 ASDF 2.33 CFFI: 0.11.2

CL-USER(1): (qs:? "crypt")

debugger invoked on a SB-BSD-SOCKETS:INTERRUPTED-ERROR in thread
debugger invoked on a SB-BSD-SOCKETS:INTERRUPTED-ERROR in thread
debugger invoked on a SB-BSD-SOCKETS:INTERRUPTED-ERROR in thread
#<THREAD "cliki-search" RUNNING {1006BEFF03}>:
debugger invoked on a SB-BSD-SOCKETS:INTERRUPTED-ERROR in thread
#<THREAD "github-search" RUNNING {100714FD03}>:
#<THREAD "bitbucket-search" RUNNING {100727FF53}>:
  Socket error in "connect": EINTR (Interrupted system call)
  Socket error in "connect": EINTR (Interrupted system call)
  Socket error in "connect": EINTR (Interrupted system call)

SEARCH-RESULTS: "crypt"

 Quicklisp
  crypt

debugger invoked on a USOCKET:TIMEOUT-ERROR in thread
#<THREAD "bitbucket-search" RUNNING {100727FF53}>:
  Condition USOCKET:TIMEOUT-ERROR was signalled.

debugger invoked on a USOCKET:TIMEOUT-ERROR in thread
#<THREAD "cliki-search" RUNNING {1006BEFF03}>:
  Condition USOCKET:TIMEOUT-ERROR was signalled.

debugger invoked on a USOCKET:TIMEOUT-ERROR in thread
#<THREAD "github-search" RUNNING {100714FD03}>:
  Condition USOCKET:TIMEOUT-ERROR was signalled.

[tkych]

Thanks for report. I'm trying to fix it, please wait.

[JuanitoFatas]

Awesome, Thanks! I found if I disable thread:

(qs:config :threading-p nil)

then it works fine!

[tkych]

I'm trying to catch the cause of this problem, but could not yet. Currently, there are 2 things might to be considered as a cause.

1. ?Garbage Collection? See, at 23:41:15 <bhyde>'s comment on http://ccl.clozure.com/irc-logs/lisp/2010-03/lisp-2010.03.02.txt
2. ?SBCL experimentally supports threading for OSX? See, http://www.sbcl.org/manual/index.html#Threading

[JuanitoFatas]

Agree with 2. Maybe we should post to usocket-dev or sbcl-dev mailing list to seek for help.