From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Simon Stapleton <simon.stapleton@gmail.com>
Cc: "15088@debbugs.gnu.org" <15088@debbugs.gnu.org>
Subject: bug#15088: 24.3; Hard crash on OSX when editing header files
Date: Fri, 16 Aug 2013 07:07:30 +0200 [thread overview]
Message-ID: <D907A600-EEE7-40E6-BE3D-20940BB36DEB@swipnet.se> (raw)
In-Reply-To: <F016CD5E-A202-4361-BCFE-A605703BFE57@gmail.com>
Hello.
I guess we can keep this bug report in case it happens again. I don't think looking at your setup will help, these things are usually compiler and/or package version dependent.
Jan D.
14 aug 2013 kl. 20:23 skrev Simon Stapleton <simon.stapleton@gmail.com>:
> Hi Jan
>
> Nope, nothing at all. So I started trying to track down what was causing the issue. Starting from a virgin .emacs.d/ and .emacs, started re-adding packages to find out which one actually breaks things.
>
> And, wouldn't you know it, I'm pretty much back to where I was before, and it no longer happens. The only thing I haven't reinstalled thus far is quack, which appears to no longer be in elpa/melpa, and shouldn't be touching C-mode files anyway.
>
> This confuses me no end, as I'd started from a virgin .emacs / emacs.d when I moved to 24.3, and re-zapped them a few times trying to get rid of this very problem.
>
> I can drop a zip/tarball of my old .emacs stuff if it would help anyone figuring out what's going on.
>
>
>
>
>
> On 13 Aug 2013, at 22:29, Jan Djärv <jan.h.d@swipnet.se> wrote:
>
>> Hello.
>>
>> 13 aug 2013 kl. 20:58 skrev Simon Stapleton <simon.stapleton@gmail.com>:
>>
>>> Okay, quick rebuild and I can now get a full backtrace. xbacktrace still fails, but it's failing because (I assume) it's had its stack smashed
>>>
>>>> No symbol "ARRAY_MARK_FLAG" in current context.
>>>
>>> ARRAY_MARK_FLAG looks a lot like a garbage collection bug being tickled, double release going on somewhere maybe?
>>>
>>> The source of the issue is almost certainly to do with pabbrev - commenting it out in my .emacs makes everything work.
>>
>> A lisp package should not be able to crash Emacs. You can try to set these in your environment before starting Emacs from the command line:
>>
>> export NSZombieEnabled=YES
>> export MallocGuardEdges=1
>> export MallocScribble=1
>> export MallocErrorAbort=1
>> export MallocCorruptionAbort=1
>> export MallocCheckHeapStart=1000
>>
>> Emacs will run very slowly, but hopefully it will print something useful if it is a memory issue.
>>
>> Jan D.
>>
>>
next prev parent reply other threads:[~2013-08-16 5:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 16:01 bug#15088: 24.3; Hard crash on OSX when editing header files Simon Stapleton
2013-08-13 18:00 ` Jan Djärv
2013-08-13 18:06 ` Simon Stapleton
2013-08-13 18:58 ` Simon Stapleton
2013-08-13 20:29 ` Jan Djärv
2013-08-14 18:23 ` Simon Stapleton
2013-08-16 5:07 ` Jan Djärv [this message]
2013-08-17 6:46 ` Simon Stapleton
2015-12-26 0:55 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D907A600-EEE7-40E6-BE3D-20940BB36DEB@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=15088@debbugs.gnu.org \
--cc=simon.stapleton@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).