From: Keith David Bershatsky <esq@lawlist.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 27571@debbugs.gnu.org
Subject: bug#27571: C stack overflow from `prin1' on deeply nested lisp object.
Date: Sun, 28 Jan 2018 15:23:47 -0800 [thread overview]
Message-ID: <m2h8r5r2ik.wl%esq@lawlist.com> (raw)
In-Reply-To: <m260f9vuyz.wl%esq@lawlist.com>
I inserted some sprintf messages in emacs.c as follows:
fprintf (stderr, "getrlimit: %d\n", getrlimit (RLIMIT_STACK, &rlim));
if (getrlimit (RLIMIT_STACK, &rlim) == 0
&& 0 <= rlim.rlim_cur && rlim.rlim_cur <= LONG_MAX)
{
fprintf (stderr, "rlim.rlim_cur: %d\n", rlim.rlim_cur);
First, I did _not_ manually set the terminal with `ulimit -S -s unlimited` -- i.e., just plain old terminal, with nothing special. The STDERR message when I open Emacs is:
getrlimit: 0
rlim.rlim_cur: 8388608
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
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
DATE: [01-28-2018 13:45:23] <28 Jan 2018 16:45:23 -0500>
FROM: Noam Postavsky <npostavs@users.sourceforge.net>
>
> Keith David Bershatsky <esq@lawlist.com> writes:
>
> * * *
>
> Can you check with gdb what the values of rlim are in this case? Around
> here, after the getrlimit call:
>
> if (getrlimit (RLIMIT_STACK, &rlim) == 0
> && 0 <= rlim.rlim_cur && rlim.rlim_cur <= LONG_MAX)
>
> On GNU/Linux, rlim.rlim_cur is 0xffffffffffffffff (or -1 if interpreted
> as a signed integer), so that if condition evaluates to false.
next prev parent reply other threads:[~2018-01-28 23:23 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 [this message]
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=m2h8r5r2ik.wl%esq@lawlist.com \
--to=esq@lawlist.com \
--cc=27571@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 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.