unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Sat, 22 Jul 2017 14:31:35 -0700	[thread overview]
Message-ID: <m24lu4kvk8.wl%esq@lawlist.com> (raw)
In-Reply-To: <m2wp72h72g.wl%esq@lawlist.com>

By process of elimination via the lo-tech method of trying different nightly builds from https://emacsformacosx.com/builds/all , I have determined that December 8, 2016 was the last build where I am able to successfully run from the terminal:

ulimit -S -s unlimited

/path/to/gui/version/emacs/built/12_08_2016

and then from the *scratch* buffer, evaluate the following:

(require 'cl-lib)

(defun make-deep-object (depth)
    (let ((obj 1))
      (while (> (cl-decf depth) 0)
        (setq obj (vector (list obj))))
      obj))

(let* ((print-circle t)
       (max-lisp-eval-depth most-positive-fixnum)
       (max-specpdl-size most-positive-fixnum)
       (deep-object (make-deep-object 6000))
       (string (prin1-to-string deep-object))
       (result (read string)))
  (when result
    (message "Success! (%d)" (length string))))

The builds that were made AFTER December 8, 2016 all crash through June 11, 2017.  At some point AFTER June 11, 2017, Emacs changed from crashing to just throwing an error message "Re-entering top level after C stack overflow".

The build of December 8, 2016 does not have `emacs-repository-version` defined, so it will be necessary to look at the commits on December 7, 2016 and December 8, 2016 to see what changed that eliminated the prior ability to use `ulimit -S -s unlimited` as a workaround to the stack overflow problem.





  parent reply	other threads:[~2017-07-22 21:31 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 [this message]
2017-07-23  2:45   ` npostavs
2017-07-23 22:28 ` Keith David Bershatsky
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=m24lu4kvk8.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).