Custom Query (1030 matches)

​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.

To reproduce:

• open the IDE
• Open a .lisp document
• make a change (add some text)
• close the document without saving
• notice there is dialog asking you if you would like to save before you close the document

To reproduce:

• Open a .lisp file in the windows IDE
• hit option (alt) . to and type in something that will be found
• hit enter
• notice it finds the item and highlights it in blue but now you can not highlight new selections.