unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: "Sheng Yang" <yangsheng6810@gmail.com>
Cc: 31995@debbugs.gnu.org
Subject: bug#31995: 26.1; Condition-case failed to catch error
Date: Wed, 11 Jul 2018 17:48:53 -0400	[thread overview]
Message-ID: <87d0vtbfzu.fsf@gmail.com> (raw)
In-Reply-To: <0af47dad-c396-7e0d-04e2-ba029a5a37d8@gmail.com> ("Sheng Yang \=\?utf-8\?B\?KOadqAnlnKMpIidz\?\= message of "Thu, 28 Jun 2018 09:54:41 -0700")

retitle 31995 Condition-case can't catch C stack overflow
tags 31995 + wontfix
quit

Sheng Yang (杨圣) <yangsheng6810@gmail.com> writes:

> It seems that the function call ~(read (current-buffer))~ causes C stack
> overflow. Though I personally believe the undo-tree file is not
> corrupted, I assume this error should be caught by condition-case even
> if the file to read is indeed corrupted.

The file is not corrupted, it's just that the recursion goes too deep
during reading.  However, I don't think condition-case can reasonably
catch C stack overflow.  As it is, recovering from C stack overflow at
all is a bit controversial, which is why we have the
attempt-stack-overflow-recovery variable which you can set to nil in
order to reliably segfault instead.





  reply	other threads:[~2018-07-11 21:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 16:54 bug#31995: 26.1; Condition-case failed to catch error Sheng Yang
2018-07-11 21:48 ` Noam Postavsky [this message]
2018-07-12  5:46   ` Sheng Yang
2018-07-13  0:29     ` Sheng Yang
2018-07-13  3:43       ` Paul Eggert

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=87d0vtbfzu.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=31995@debbugs.gnu.org \
    --cc=yangsheng6810@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).