all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: 23233@debbugs.gnu.org
Subject: bug#23233: 25.0.92; Crash after doing much work in Proof General
Date: Thu, 07 Apr 2016 00:13:05 +0200	[thread overview]
Message-ID: <m3h9fez8r2.fsf@gnus.org> (raw)
In-Reply-To: <m2twjeh0u5.fsf@newartisans.com> (John Wiegley's message of "Wed,  06 Apr 2016 14:41:22 -0700")

John Wiegley <jwiegley@gmail.com> writes:

>>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>
>> 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?
>
> I suppose it's always possible, but I wonder then why I don't see this more
> often. I'll look for recursions the next time it happens. For now, I'll keep
> Emacs under lldb with full debugging (which does make it noticeably slower).

Well, an infinite hook recursion still shouldn't make Emacs crash.

The backtrace reminded me a bit about the known gc recursion bug that I
can't remember the recipe for right now -- it was something about if you
(setcar foo foo), then Emacs will segfault when trying to gc?  I forget
the details, but it's in the debbugs somewhere.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2016-04-06 22:13 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
2016-04-06 21:41   ` John Wiegley
2016-04-06 22:13     ` Lars Magne Ingebrigtsen [this message]
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=m3h9fez8r2.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=23233@debbugs.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.