GNU bug report logs -
#31995
Condition-case can't catch C stack overflow
Previous Next
Reported by: Sheng Yang (杨圣) <yangsheng6810 <at> gmail.com>
Date: Thu, 28 Jun 2018 17:02:02 UTC
Severity: normal
Tags: wontfix
Found in version 26.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
retitle 31995 Condition-case can't catch C stack overflow
tags 31995 + wontfix
quit
Sheng Yang (杨圣) <yangsheng6810 <at> 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.
This bug report was last modified 5 years and 325 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.