From: Ivan Andrus <darthandrus@gmail.com>
To: Emacs Dev <emacs-devel@gnu.org>
Subject: Re: Investigating crash (Bug#11395) on Mac OS
Date: Wed, 9 May 2012 21:23:57 +0200 [thread overview]
Message-ID: <1F4745AE-7674-4807-970D-19C702774A51@gmail.com> (raw)
In-Reply-To: <87havwxmbs.fsf@gnu.org>
On May 4, 2012, at 12:38 PM, Chong Yidong wrote:
> Ivan Andrus <darthandrus@gmail.com> 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.
-Ivan
next prev parent reply other threads:[~2012-05-09 19:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 2:32 Investigating crash (Bug#11395) on Mac OS Chong Yidong
2012-05-04 2:58 ` Liang Wang
2012-05-07 17:36 ` Randal L. Schwartz
2012-05-08 2:40 ` Chong Yidong
2012-05-09 16:59 ` Felix Geller
2012-05-04 8:07 ` Ivan Andrus
2012-05-04 10:38 ` Chong Yidong
2012-05-09 19:23 ` Ivan Andrus [this message]
2012-05-11 13:24 ` Chong Yidong
2012-05-04 16:50 ` Glenn Morris
2012-05-05 16:53 ` chad
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1F4745AE-7674-4807-970D-19C702774A51@gmail.com \
--to=darthandrus@gmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.