[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: Wed, 9 May 2012 21:23:57 +0200

On May 4, 2012, at 12:38 PM, Chong Yidong wrote:

> Ivan Andrus <address@hidden> writes:
>> 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.
> If this is right, there may have been a fix committed to trunk but
> missing from the release branch (since Bug#11395 was reported for the
> 24.0.96 pretest).
> If you can, please try bisecting.  That would help tremendously.  The
> (so far incomplete) recipe posted by Richard Stanton in the bug page for
> Bug#11395 may help if you can reproduce it.

My attempts at bisecting were an utter failure.  First I had problems building 
after using bzr bisect so I decided to bisect "manually".  I was able to easily 
reproduce the problem with some revisions e.g. 108034 by repeatedly exporting 
an org file to pdf (only required 3-5 exports).  I was unable (after 10-15 
exports) to reproduce the problem with other revisions e.g. 108049.  I had to 
leave it though, and now that I come back to it I can't reproduce the problem 
with revision 108034.  So there's something weird going on.

FWIW I was trying to bisect "backwards" by finding the revision where it was 
fixed for me.  There were far fewer commits that way since I hadn't previously 
updated for about a month.

>> IIRC running it under valgrind, which would be my first instinct,
>> isn't supported.
> Running `valgrind ./temacs -l loadup' works for me (apart from the usual
> cloud of false positives due to GC).  But maybe it doesn't work on Mac
> OS, I dunno.

That's good to know.  But `valgrind ./emacs` wouldn't work I assume?  Anyway, 
I'll try it later if I can reproduce the error.


reply via email to

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