283: Thread safety: libc functions
There are places that we call unsafe-for-threading libc functions
that we should find alternatives for, or put locks around. Known or
- strongly suspected problems, as of 0.8.3.10: please update this
+ strongly suspected problems, as of 1.0.3.13: please update this
bug instead of creating new ones
- gethostbyaddr in sb-bsd-sockets
-
284: Thread safety: special variables
There are lots of special variables in SBCL, and I feel sure that at
least some of them are indicative of potentially thread-unsafe
(defsystem sb-bsd-sockets
:version "0.58"
- :depends-on (sb-grovel)
+ :depends-on (sb-grovel)
#+sb-building-contrib :pathname
#+sb-building-contrib "SYS:CONTRIB;SB-BSD-SOCKETS;"
:components ((:file "defpackage")
"win32-constants"
:package :sockint
:depends-on ("defpackage" "win32-lib"))
- #+win32 (:file "win32-sockets"
+ #+win32 (:file "win32-sockets"
:depends-on ("win32-constants"))
(:file "sockets"
- :depends-on #-win32 ("constants")
+ :depends-on #-win32 ("constants")
#+win32 ("win32-sockets"))
(:file "sockopt" :depends-on ("sockets"))
(:file "inet" :depends-on ("sockets" "split"))
;; (:static-file "INSTALL")
;; (:static-file "README")
;; (:static-file "index" :pathname "index.html")
- (:static-file "doc" :pathname "doc.lisp")
(:static-file "TODO")))
(defmethod perform :after ((o load-op) (c (eql (find-system :sb-bsd-sockets))))