From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r117741: Handle C stack overflow caused by too nested Lisp evaluation.
Date: Wed, 27 Aug 2014 01:04:59 -0400 [thread overview]
Message-ID: <jwvtx4ya5ic.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <53FD4DD2.6050204@yandex.ru> (Dmitry Antipov's message of "Wed, 27 Aug 2014 07:17:38 +0400")
>>> + DEFVAR_LISP ("top-level-message", Vtop_level_message,
>>> + doc: /* Message displayed by `normal-top-level'. */);
>> Why does this need to be exported to Elisp?
> This is just to allow 'normal-top-level' to display an appropriate message.
Then please name it "internal--top-level-message" or somesuch.
>>> + /* Hard GC error may lead to stack overflow caused by
>>> + too nested calls to mark_object. No way to survive. */
>> I don't see why there's no way to survive. Isn't it safe to interrupt
>> GC within the mark phase and re-run it?
> Maybe (at least, it requires some more work). But if we get SIGSEGV in GC,
> most likely we have 1) too deep data structures or 2) fatal error,
> probably invalid pointer. Since I don't see a way to recover in either
> case, I don't see how restarting GC can help.
Right, we should just abort.
Stefan
prev parent reply other threads:[~2014-08-27 5:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XMAE8-00085O-Du@vcs.savannah.gnu.org>
2014-08-26 18:37 ` [Emacs-diffs] trunk r117741: Handle C stack overflow caused by too nested Lisp evaluation Stefan Monnier
2014-08-27 3:17 ` Dmitry Antipov
2014-08-27 5:04 ` Stefan Monnier [this message]
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=jwvtx4ya5ic.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dmantipov@yandex.ru \
--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.