[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Investigating crash (Bug#11395) on Mac OS

From: Ivan Andrus
Subject: Re: Investigating crash (Bug#11395) on Mac OS
Date: Fri, 4 May 2012 10:07:57 +0200

On May 4, 2012, at 4:32 AM, Chong Yidong wrote:

> Could someone who is running on Mac OS please help investigate the crash
> reported at
>  http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11395
> ?  It's claimed to be reproducible, but I can't get it to crash on my
> end (x86_64-unknown-linux-gnu), so maybe some part of the Nextstep code
> is not GC-safe.
> Thanks.

I was getting this quite regularly (about every 15 minutes) a week ago (from 
bzr head), but after I got done traveling (Tuesday) I updated and I haven't 
experienced it since.  I assumed someone had fixed it so I didn't bother 
reporting it.  In the past several years it has been very stable updating from 
bzr head every so often.  So at least for me it's been very version dependent.

When I debugged it once it was stuck in a loop with internal_condition_case 
returning 0 (instead of Qnil) or something like that.  I also remember one time 
when the window information got corrupted in some way so that point-min wasn't 
a marker.  The result was that I couldn't do anything including closing the 
window because it would error.

So it seems it's probably (random) memory corruption, but you probably knew 
that.  Why it's fixed now for me, I don't know.  If you would like I could try 
and bisect to see what changed. Hopefully it's not dependent on the phase of 
the moon. :-)  Is there anything else I could do to try and figure it out?  
IIRC running it under valgrind, which would be my first instinct, isn't 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]