From: Simon Stapleton <simon.stapleton@gmail.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 15088@debbugs.gnu.org
Subject: bug#15088: 24.3; Hard crash on OSX when editing header files
Date: Tue, 13 Aug 2013 20:58:27 +0200 [thread overview]
Message-ID: <868509D1-DEA1-479F-BB3F-65C218AED0E1@gmail.com> (raw)
In-Reply-To: <3F83BB9B-EA61-4D72-A101-63AE305C3067@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.
Simon
On 13 Aug 2013, at 20:06, Simon Stapleton <simon.stapleton@gmail.com> wrote:
> Hi Jan.
>
> On 13 Aug 2013, at 20:00, Jan Djärv <jan.h.d@swipnet.se> wrote:
>
>>> xbacktrace doesn't do anything on my gdb. Go figure.
>>
>> You have to be in the emacs source src/ directory, and do
>> % gdb ../nextstep/Emacs.app/Contents/MacOS/Emacs
>>
>> or otherwise make gdb read the .gdbinit in the src/ directory.
>
> Re-downing the source right now, will rebuild and test.
>
>>> My suspicion is that pabbrev is triggering the issue, but quite how, I don't know.
>>
>> How would that be involved if you started with -Q?
>
> <insert palm-forehead sound here>
>
> With -Q, no crash. Which means it's probably not a core emacs bug, but rather an elisp issue somewhere that's causing badness, right?
>
> Any ideas on how I should go about chasing it down?
>
> Cheers
>
> Simon
next prev parent reply other threads:[~2013-08-13 18:58 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 [this message]
2013-08-13 20:29 ` Jan Djärv
2013-08-14 18:23 ` Simon Stapleton
2013-08-16 5:07 ` Jan Djärv
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=868509D1-DEA1-479F-BB3F-65C218AED0E1@gmail.com \
--to=simon.stapleton@gmail.com \
--cc=15088@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
/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).