Custom Query (1030 matches)

After upgrading my Arch Linux kernel to 3.15, Clozure consistantly aborts with a "Clozure CL kernel debugger: " prompt.

In gdb:

$ gdb ./lx86cl64
...
(gdb) run --image-name lx86cl64.image --no-init
Starting program: /home/local64-arch/apps/ccl-1.9/lx86cl64 --image-name lx86cl64.image --no-init
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
x86_early_exception_init () at ../x86-exceptions.c:106
106	  do_intn();
(gdb) 

From the comments in x86-exceptions.c, evidently the workaround for handling exceptions has been broken.

​http://clozure.com/pipermail/openmcl-devel/2011-January/012498.html

describes a problem which affected someone running ARM Linux. It's not clear what Linux versions and architectures are affected.

Traditionally, Linux maps in pages of the initial thread's control/C stack as they're touched. The new (or at least previously unobserved) behavior involves the kernel not mapping a page that would be adjacent to another mapped region (like the guard page region that CCL uses to detect stack overflow) and causes the stack limit check in the recursive marker to fail.

I think that the simplest fix is likely to ensure that all pages between the stack area's softlimit and current sp are mapped read-write, so that the kernel's lazy faulting-in of stack pages doesn't try to exercise policy.

We don't provide interface databases that include new Leopard stuff (like NSGradient, for example).

At some fairly near future date, we might want to build interfaces with -mmacosx-version-min=10.5 or come up with some scheme to allow the user to switch between various versions.