[Openmcl-devel] ARM testing

Gary Byers gb at clozure.com
Sun Jan 30 04:14:55 UTC 2011



On Thu, 27 Jan 2011, David Brown wrote:

> On Thu, Jan 27 2011, Gary Byers wrote:
>
>> On Thu, 27 Jan 2011, David Brown wrote:
>
>> In that case, we're running into the write-protected guard pages at the end
>> of the listener thread's control stack; the same sequence of events happens
>> for me if I do:
>>
>> ? (process-interrupt ccl::*initial-process* #'foo 0)
>
>> If foreign code (including the GC, including rmark()) tries to write
>> to those guard pages we expect to get a SIGSEGV; in general, it's
>> harder to
>> recover from an exception in foreign code, and I think that we just drop
>> into the kernel debugger in that case.  (Or at least try to.)
>>
>> Do you get a STACK-OVERFLOW condition signaled in lisp ?  Or does this just
>> die with SIGBUS ? Or does something else happen ?
>
> It dies with a SIGBUS.

Just to be sure: do you get a lisp-level STACK-OVERFLOW condition when that
function runs on the listener thread, and a SIGBUS on the initial thread ?
Or a SIGBUS on either thread ?




More information about the Openmcl-devel mailing list