Custom Query (1030 matches)

If we get an unrecoverable memory fault, we try to use the siginfo_t argument to the signal handler to describe the reason for the fault.

On Darwin, we handle exceptions at the Mach level and create the siginfo_t argument ourselves. I think that we do this to make the fault address easier to find, but I don't think that we set other fields in the siginfo_t to meaningful values, so the attempt to describe those fields often gives misleading results.

We should presumably either try harder to initialize the siginfo_t the way that a real SIGBUS or SIGSEGV would, or not trust our ability to describe the fault accurately.

If I DELETE-PACKAGE a package, which is the current package, I get

Error: #<Deleted Package> is a deleted package . While executing: #<error printing #<Recursive printing error> #x30004001A4BE> #x3000400CD6EE>, in process listener(1).

And CCL ends up in the kernel debugger, when i try to call functions with unqualified names.

Consider the following code, which is a simplified version of stuff that can be found in CL-Yacc:

(defstruct item x)
(defstruct (sub-item (:include item) (:conc-name item-)) y)

The ANSI CL spec explicitly states that this is allowed, in the description of :CONC-NAME in the description of DEFSTRUCT. However, CCL generates a warning:

;Compiler warnings for "/home/pps/jch/struct-test.lisp" :
;   In an anonymous lambda form at position 18: Duplicate definitions of ITEM-X, in this file

It would appear that CCL generates correct code, but I believe that this is by accident.