From: Keith David Bershatsky <esq@lawlist.com>
To: npostavs@users.sourceforge.net
Cc: 27779@debbugs.gnu.org
Subject: bug#27779: 26.0.50: read -- Re-entering top level after C stack overflow
Date: Sun, 23 Jul 2017 15:28:40 -0700 [thread overview]
Message-ID: <m2h8y2g547.wl%esq@lawlist.com> (raw)
In-Reply-To: <m2wp72h72g.wl%esq@lawlist.com>
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
This is a work in progress, but here is a partial:
The first time I see a break in the prior expected behavior was on 11/19/2017 (c61ee94959ba96b2a327df0684593f7e569e30be) when portions of Emacs 25 were merged with the master branch and `emacs.c` was modified. Here is a partial reversal of the code that broke the ability to avoid a stack overflow by setting `ulimit -S -s unlimited`. The patch applies to the above-mentioned head -- i.e., the patch will apply following a hard reset.
I have not yet been able to follow the subsequent breaks to avoid a stack overflow with the current master branch.
[-- Attachment #2: patch_5e2ae74df54d4090c591c79ab13e7713c6654b9c.diff --]
[-- Type: application/diff, Size: 3552 bytes --]
next prev parent reply other threads:[~2017-07-23 22:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 2:12 bug#27779: 26.0.50: read -- Re-entering top level after C stack overflow Keith David Bershatsky
2017-07-21 3:03 ` Keith David Bershatsky
2017-07-22 3:24 ` npostavs
2017-07-22 5:52 ` Keith David Bershatsky
2017-07-22 12:05 ` npostavs
2017-07-22 16:32 ` Keith David Bershatsky
2017-07-22 17:23 ` npostavs
2017-07-22 21:31 ` Keith David Bershatsky
2017-07-23 2:45 ` npostavs
2017-07-23 22:28 ` Keith David Bershatsky [this message]
2018-01-09 1:38 ` bug#27779: #27779; C stack overflow from `read' on deeply nested lisp object Keith David Bershatsky
2018-06-06 21:04 ` Vasilij Schneidermann
2018-06-06 21:30 ` Noam Postavsky
2018-06-07 8:18 ` Vasilij Schneidermann
2019-05-02 2:30 ` Noam Postavsky
2019-05-02 7:05 ` Keith David Bershatsky
2019-05-02 7:26 ` Paul Eggert
2019-05-02 8:00 ` Keith David Bershatsky
2022-04-21 13:33 ` bug#27779: 26.0.50: read -- Re-entering top level after C stack overflow Lars Ingebrigtsen
2022-04-21 18:56 ` Keith David Bershatsky
2022-04-22 0:26 ` 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=m2h8y2g547.wl%esq@lawlist.com \
--to=esq@lawlist.com \
--cc=27779@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).