Custom Query (1030 matches)

Having a PROCESS-PLIST accessor on PROCESS instances would be very helpful and appears to have benign consequences for existing code. This permits us to associate other items of interest with all processes, e.g., a PID (process descriptor) which can be used to encapsulate a lot of other information (e.g., mailboxes, locks, types of processes, etc.) without actually extending the PROCESS class object beyond the property list slot.

This is needed because calling make-process uses an existing class definition by default. New instances can be applied to extended class definitions using the :CLASS keyword parameter. But existing processes will not have the features needed by extended process objects. And the listener process, and perhaps others, will have already been created, yet need to participate with other instances in these extended applications.

By adding a PLIST slot with accessor CCL:PROCESS-PLIST we can associate arbitrary extensions with already existing processes as needed by applications.

(defclass process () .... (PLIST :INITFORM NIL :ACCESSOR PROCESS-PLIST) ...)

• DM

On a long running server process, ClozureCL crashed in networking code. The server uses Hunchentoot.

Welcome to Clozure Common Lisp Version 1.3-dev-r11784M-trunk (LinuxX8664)!

Exception occurred while executing foreign code
? for help
[12821] Clozure CL kernel debugger: B
current thread: tcr = 0x404c77c0, native thread ID = 0x3217, interrupts enabled
(#x00002AAAAC6D99E8) #x0000300040085F04 : #<Function MALLOC #x0000300040085E6F> + 149
(#x00002AAAAC6D9A00) #x00003000402D540C : #<Function %MAKE-HEAP-IVECTOR #x00003000402D536F> + 157
(#x00002AAAAC6D9A40) #x00003000402D4504 : #<Function MAKE-HEAP-IVECTOR #x00003000402D440F> + 245
(#x00002AAAAC6D9A78) #x0000300040334E94 : #<Function INIT-STREAM-IOBLOCK #x0000300040334ACF> + 965
(#x00002AAAAC6D9BE8) #x000030004033332C : #<Function MAKE-IOBLOCK-STREAM #x00003000403331AF> + 381
(#x00002AAAAC6D9C20) #x00003000403314C4 : #<Function MAKE-FD-STREAM #x00003000403310BF> + 1029
(#x00002AAAAC6D9D38) #x00003000406091D4 : #<Function ACCEPT-SOCKET-CONNECTION #x000030004060905F> + 373
(#x00002AAAAC6D9DA8) #x000030004018F5F4 : #<Function %%CHECK-KEYWORDS #x000030004018F50F> + 229
(#x00002AAAAC6D9E20) #x0000300041A1CCD4 : #<Function (:INTERNAL OPEN-SOCKET-AND-ACCEPT START-UP-SERVER) #x0000300041A1C7CF> + 1285
(#x00002AAAAC6D9EB8) #x00003000404AB97C : #<Function RUN-PROCESS-INITIAL-FORM #x00003000404AB6AF> + 717
(#x00002AAAAC6D9F48) #x00003000404AC584 : #<Function (:INTERNAL (%PROCESS-PRESET-INTERNAL (PROCESS))) #x00003000404AC3FF> + 389
(#x00002AAAAC6D9F98) #x000030004048D10C : #<Function (:INTERNAL THREAD-MAKE-STARTUP-FUNCTION) #x000030004048CFDF> + 301
[12821] Clozure CL kernel debugger: T
Current Thread Context Record (tcr) = 0x404c77c0
Control (C) stack area:  low = 0x40274000, high = 0x404c8000
Value (lisp) stack area: low = 0x2aaaac4c9000, high = 0x2aaaac6da000
Exception stack pointer = 0x404c6ca0
[12821] Clozure CL kernel debugger: R
%rax = 0x0000000000000051      %r8  = 0x0000000000000001
%rcx = 0x00002aaab0000090      %r9  = 0x00002aaab0000048
%rdx = 0x00002aaab0008810      %r10 = 0x00002aaab0000078
%rbx = 0x0000000000000001      %r11 = 0x00000000004204d0
%rsp = 0x00000000404c6ca0      %r12 = 0x0000000000000050
%rbp = 0x00002aaab0005b20      %r13 = 0x0000000000000020
%rsi = 0x0000000000000419      %r14 = 0x00002aaab0000080
%rdi = 0x00002aaab0000020      %r15 = 0x00002aaab0000020
%rip = 0x00002aaaab3dea1b   %rflags = 0x00010202

When running a loop-back test for an extended period of time, the computer goes into screen saving mode, and Clozure server sockets shut down, refusing any further (re)connections. This is not a one-time event. I see it repeatedly after many such trials.

The message from the client side, after receiving a time out on an awaited reply, and then attempting to reconnect, is:

Error making TCP connection: host="Amethyst.local", service=12010,

reason=Failed to connect: Connection refused (61).

(That (61) may be a locally generated error? or it may be a Unix error number?)