From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: 23233@debbugs.gnu.org
Subject: bug#23233: 25.0.92; Crash after doing much work in Proof General
Date: Wed, 06 Apr 2016 22:48:45 +0300 [thread overview]
Message-ID: <83twjeldr6.fsf@gnu.org> (raw)
In-Reply-To: <m237qyilgq.fsf@newartisans.com> (message from John Wiegley on Tue, 05 Apr 2016 22:08:53 -0700)
> From: John Wiegley <jwiegley@gmail.com>
> Date: Tue, 05 Apr 2016 22:08:53 -0700
>
> After using Emacs (built just today) for many hours, I found myself needing to
> kill a Coq buffer, which apparently prompted a GC. It was during this GC that
> it died.
>
> Nothing that I was doing was out of the ordinary for me, and Emacs has been
> running strong for weeks, so there's a subtle edge case here that I'm unable
> to reduce into something smaller.
>
> I'm reporting this in case it's something that can be gleaned from reading the
> trace. Otherwise, feel free to close and I will keep looking for a pattern.
>
> http://dl.dropbox.com/u/137615/info.txt
How much stack do you have there for the Emacs executable? The stack
trace looks like infinite recursion to me, repeating this sequence ad
nauseam:
frame #27912: 0x0000000100330ae4 Emacs`call1 + 68
frame #27913: 0x000000010034d407 Emacs`mapcar1 + 1095
frame #27914: 0x0000000100350fc5 Emacs`Fmapcar + 15109
frame #27915: 0x000000010032fac8 Emacs`Ffuncall + 1432
frame #27916: 0x00000001003bf9bc Emacs`exec_byte_code + 5196
frame #27917: 0x00000001003319e3 Emacs`funcall_lambda + 2739
frame #27918: 0x000000010032fdeb Emacs`Ffuncall + 2235
frame #27919: 0x00000001003bf9bc Emacs`exec_byte_code + 5196
frame #27920: 0x00000001003319e3 Emacs`funcall_lambda + 2739
frame #27921: 0x000000010032fdeb Emacs`Ffuncall + 2235
with minor variations. This starts from running a hook:
frame #28069: 0x000000010033072c Emacs`run_hook_with_args + 1308
frame #28070: 0x00000001003301f4 Emacs`Frun_hook_with_args + 36
frame #28071: 0x00000001003301bf Emacs`run_hook + 31
frame #28072: 0x0000000100330177 Emacs`Frun_hooks + 55
so maybe one of your hooks incurs infinite recursion?
next prev parent reply other threads:[~2016-04-06 19:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 5:08 bug#23233: 25.0.92; Crash after doing much work in Proof General John Wiegley
2016-04-06 19:48 ` Eli Zaretskii [this message]
2016-04-06 21:41 ` John Wiegley
2016-04-06 22:13 ` Lars Magne Ingebrigtsen
2016-04-06 22:24 ` Andreas Schwab
2016-04-07 2:45 ` Eli Zaretskii
2016-04-07 15:12 ` Markus Triska
2016-04-07 2:41 ` Eli Zaretskii
2016-12-07 19:47 ` Glenn Morris
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=83twjeldr6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23233@debbugs.gnu.org \
--cc=jwiegley@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 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.