Custom Query (1030 matches)

ccl:receive-from signals "Interrupted system call (error #4) during recvfrom". Typically happens when this is run in a thread.

(process-run-function "udp reader"
                      (lambda ()
                        (let ((socket (ccl:make-socket
                                       :type :datagram
                                       :reuse-address t
                                       :external-format '(unsigned-byte 8)
                                       :format :binary
                                       :local-port 0)))
                          (handler-case
                              (ccl:receive-from socket 32000)
                            (error (c)
                              (format t "Receive-from error: ~a" c))))))

If I run above and type :proc, I get:

Receive-from error: on #<CCL::UDP-SOCKET #x89DFD3E> : 
Interrupted system call (error #4) during recvfrom
8 :    udp reader   [Active]  (Suspended)
1 : -> listener     [Active] 
0 :    Initial      [Sleep] 

(lisp-implementation-version) "Version 1.3-RC1-r11719M (DarwinPPC32)"

I wrote some code to exercise CCL's math functions and found that there were cases where intermediate computations were causing floating point overflows.

Functions affected are exp, tan, atan, tanh and atanh:

exp: fails for very large negative real rationals.

tanh: fails for complex arguments with very large real parts.

atanh: fails for numbers of the form 1 + iy for very small y.

tan and atan: analogous failures as for tanh and atanh.

I'm attaching (i) the code to exercise the functions (you just load it into Lisp) and (ii) a file of patches that fix the issues. (Apart from the exp issue, these are present in the fix to 869 - sorry.)

The contents of an instance of gui:ns-lisp-string always prints as the empty string. This seems to be because gui:ns-lisp-strings answer NIL to initialized-nsobject-p, which results in their nsobject-description being the empty string.

Probably should change the nsobject-description of uninitialized objects to "[uninitialized]" or something like that while you're at it.