From: npostavs@users.sourceforge.net
To: Keith David Bershatsky <esq@lawlist.com>
Cc: 27571@debbugs.gnu.org
Subject: bug#27571: Crashing when printing a lisp object.
Date: Thu, 06 Jul 2017 22:46:40 -0400 [thread overview]
Message-ID: <87fue9ge0f.fsf@users.sourceforge.net> (raw)
In-Reply-To: <eftwzws3.wl%esq@lawlist.com> (Keith David Bershatsky's message of "Mon, 03 Jul 2017 20:49:32 -0700")
retitle 27571 C stack overflow from `prin1' on deeply nested lisp object.
severity 27571 minor
tags 27571 + confirmed
quit
Keith David Bershatsky <esq@lawlist.com> writes:
> Yes, 'ulimit -S -s unlimited', does indeed fix the problem! :) :) :)
>
> Yes, my line 1350 of print.c is the opening brace for print_object.
>
> I will hunt around in `main` for ways to increase the stack size
> limit, as well as research other means to have the settings take
> effect whenever launching the GUI version of Emacs.
The proper fix would be to rewrite print_object to avoid recursion and
use an explicit stack instead.
next prev parent reply other threads:[~2017-07-07 2:46 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 [this message]
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
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=87fue9ge0f.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 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.