[Openmcl-devel] YAWC (Yet Another Weird Crash)

Gary Byers gb at clozure.com
Fri May 29 08:01:33 UTC 2009


I was eventually able to get this to crash; when it did, it generated
a Crash Reporter log file.  I opened a ticket

<http://trac.clozure.com/openmcl/ticket/518>

describing the little bit that we know so far and attached that crash
report.

It seems to show that two threads (the event thread and an NSThread
created by some foreign code) were in the same place in #_malloc()
(though presumably in different malloc "zones") and the foreign
NSThread segfaulted.  That's about all I know at this point.

On Fri, 29 May 2009, Gary Byers wrote:

> You were able to create a separate thread and otherwise recreate a
> similar threading environment in ObjC, then ?
>
> Surprising that that'd work; I would have guessed that this was a
> threading issue.
>
> On Thu, 28 May 2009, Ron Garret wrote:
>
>>
>> On May 28, 2009, at 5:02 PM, Ron Garret wrote:
>>
>>> 5.  My next step is try to reproduce this in pure ObjC.
>>
>> Nope, ObjC happily switches back and forth between two PDFs all day long.  So
>> this must be a CCL issue.
>>
>> rg
>>
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel
>
>



More information about the Openmcl-devel mailing list