From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: 27571@debbugs.gnu.org
Subject: bug#27571: C stack overflow from `prin1' on deeply nested lisp object.
Date: Sun, 28 Jan 2018 19:13:40 -0500 [thread overview]
Message-ID: <87bmhdjzd7.fsf@users.sourceforge.net> (raw)
In-Reply-To: <m2fu6pr1b9.wl%esq@lawlist.com> (Keith David Bershatsky's message of "Sun, 28 Jan 2018 15:49:46 -0800")
Keith David Bershatsky <esq@lawlist.com> writes:
>> > Second, I _did_ manually set the terminal with `ulimit -S -s
>> > unlimited`. The STDERR message when I open Emacs is:
>> >
>> > getrlimit: 0
>> >
>> > rlim.rlim_cur: 67104768
> Starting a fresh terminal session, with no special settings:
>
> $ ulimit -H -s
>
> 65532
Ah, 65532 * 1024 = 67104768, so there we are. You just need to figure
out if and how that limit can be lifted.
next prev parent reply other threads:[~2018-01-29 0:13 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 ` bug#27571: " Noam Postavsky
2018-01-09 16:33 ` bug#27571: #27571; " 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 [this message]
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
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=87bmhdjzd7.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=27571@debbugs.gnu.org \
--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 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).