From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: 27571@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#27571: C stack overflow from `prin1' on deeply nested lisp object.
Date: Tue, 09 Jan 2018 07:58:34 -0500 [thread overview]
Message-ID: <874lnvqjd1.fsf_-_@users.sourceforge.net> (raw)
In-Reply-To: <m2wp0rke01.wl%esq@lawlist.com> (Keith David Bershatsky's message of "Mon, 08 Jan 2018 17:38:38 -0800")
Keith David Bershatsky <esq@lawlist.com> writes:
> I have determined that bug #27571 was introduced on November 19, 2016
> with commit c61ee94959ba96b2a327df0684593f7e569e30be. The following
> patch to the Emacs 26 branch as of today (01/08/2018) reverses the
> commit and enables the test below to be completed successfully.
>
> [FYI: I am on OSX 10.6.8 and am manually increasing the stack limit
> with `ulimit -S -s unlimited` so that I can have rather large custom
> undo-tree histories.]
By "broken" you mean that it prevents the `ulimit -S -s unlimited` trick
from working? Perhaps it's just a matter of detecting this "unlimited"
case explicitly.
next prev parent reply other threads:[~2018-01-09 12:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 1:42 bug#27571: Crashing when printing a lisp object Keith David Bershatsky
2017-07-04 2:05 ` npostavs
2017-07-04 2:32 ` Keith David Bershatsky
2017-07-04 3:32 ` npostavs
2020-08-24 14:11 ` Lars Ingebrigtsen
2020-10-01 1:59 ` Lars Ingebrigtsen
2017-07-04 3:49 ` Keith David Bershatsky
2017-07-07 2:46 ` npostavs
2017-07-26 1:14 ` Keith David Bershatsky
2018-01-09 1:38 ` bug#27571: #27571; C stack overflow from `prin1' on deeply nested " Keith David Bershatsky
2018-01-09 7:53 ` Paul Eggert
2018-01-09 12:58 ` Noam Postavsky [this message]
2018-01-09 16:33 ` Keith David Bershatsky
2018-01-09 16:43 ` bug#27571: " Keith David Bershatsky
2018-01-28 21:45 ` Noam Postavsky
2018-01-28 23:23 ` Keith David Bershatsky
2018-01-28 23:43 ` Noam Postavsky
2018-01-28 23:49 ` Keith David Bershatsky
2018-01-29 0:13 ` Noam Postavsky
2018-01-29 4:26 ` Keith David Bershatsky
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=874lnvqjd1.fsf_-_@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=27571@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=esq@lawlist.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.