[Openmcl-devel] test version of Mojave-compatible app store ccl

R. Matthew Emerson rme at acm.org
Mon Nov 19 16:40:44 UTC 2018



> On Nov 19, 2018, at 1:06 AM, Rainer Joswig <joswig at lisp.de> wrote:
> 
> Hi,
> 
> is it related to the following?

Yes, I'm pretty certain that this crash-on-quit is a related symptom.





> 
> 
> Mac:~ rj$ time ccl64 --eval '(quit)'
> 
> real	0m0.023s
> user	0m0.009s
> sys	0m0.012s
> Mac:~ rj$ time ccl64 --eval '(quit)'
> 
> real	0m0.024s
> user	0m0.009s
> sys	0m0.012s
> Mac:~ rj$ time ccl64 --eval '(quit)'
> 
> real	0m0.024s
> user	0m0.009s
> sys	0m0.011s
> Mac:~ rj$ time ccl64 --eval '(quit)'
> Unhandled exception 4 at 0x7fff71dceb53, context->regs at #x70000718c590
> ? for help
> [9382] Clozure CL kernel debugger: 
> 
> 
> I can call CCL with a QUIT function call several times and in random intervals (one out of ten calls on a mostly idle machine) it crashes on exit.
> 
> I've built the ccl64 from the latest Github version (yesterday) like described in the issue 150.
> 
> ccl64 --version
> Version 1.12-dev (v1.12-dev.3-44-g8fa7fdfc) DarwinX8664
> 
> OS version is macOS 10.14.1
> 
> 
> Regards,
> 
> Rainer
> 
> 
> 
>> Am 13.11.2018 um 23:31 schrieb R. Matthew Emerson <rme at acm.org <mailto:rme at acm.org>>:
>> 
>> 
>> 
>>> On Nov 13, 2018, at 2:28 PM, Dave Cooper <david.cooper at genworks.com <mailto:david.cooper at genworks.com>> wrote:
>>> 
>>> 
>>> 
>>> I wish I remembered why we needed the DarwinSigReturn workaround in the first place.  It looks like it is going to be necessary to detect at runtime whether we are on a pre-Mojave macOS, and leave the DarwinSigReturn thing in place if so.
>>> 
>>> 
>>> Hi Matt,
>>> 
>>> Is there anything else I can do to help with this? Should this be  a github Issue, or be included in the discussion of https://github.com/Clozure/ccl/issues/150 <https://github.com/Clozure/ccl/issues/150>? 
>>> 
>>> Dave
>>> 
>>> 
>> 
>> I just need to find the time to come up with a fix.  https://github.com/Clozure/ccl/issues/146 <https://github.com/Clozure/ccl/issues/146> would be the right place for this.  It cites your test case.
>> 
>> _______________________________________________
>> Openmcl-devel mailing list
>> Openmcl-devel at clozure.com <mailto:Openmcl-devel at clozure.com>
>> https://lists.clozure.com/mailman/listinfo/openmcl-devel
> 
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> https://lists.clozure.com/mailman/listinfo/openmcl-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clozure.com/pipermail/openmcl-devel/attachments/20181119/bbd5608c/attachment.html>


More information about the Openmcl-devel mailing list