all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Mon, 03 Jul 2017 22:05:12 -0400	[thread overview]
Message-ID: <87bmp1hs87.fsf@users.sourceforge.net> (raw)
In-Reply-To: <m260f9vuyz.wl%esq@lawlist.com> (Keith David Bershatsky's message of "Mon, 03 Jul 2017 18:42:12 -0700")

Keith David Bershatsky <esq@lawlist.com> writes:

> [cl-struct-undo-tree [nil ([nil ...

Is this the struct that crashes when printing, or one that's just under
the threshold?  (I don't get any crash here)

> The persistent undo history feature uses `prin1` to create a printed
> representation of the undo-tree history, which is saved to a file and
> then restored at a later point in time with the `read` command.  Emacs
> 25.2.1 is crashing on OSX Snow Leopard and also OSX El Capitan when
> the undo tree history exceeds a count of approximately 6651.
>
>     Program received signal SIGSEGV, Segmentation fault.
>     0x0000000100141da7 in print_object (obj=4790542093, printcharfun=0, 
>         escapeflag=true) at print.c:1350
>     1350	{

Line 1350 is just at the beginning of print_object, right?  I'm guessing
you're just overflowing the stack.  Can you increase it with ulimit or
something?





  reply	other threads:[~2017-07-04  2:05 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 [this message]
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
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=87bmp1hs87.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.