From: Keith David Bershatsky <esq@lawlist.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
npostavs@gmail.com, mail@vasilij.de, 27779@debbugs.gnu.org
Subject: bug#27779: 26.0.50: read -- Re-entering top level after C stack overflow
Date: Thu, 21 Apr 2022 11:56:35 -0700 [thread overview]
Message-ID: <m21qxqmfj0.wl%esq@lawlist.com> (raw)
In-Reply-To: <m2wp72h72g.wl%esq@lawlist.com>
As to the most recent versions of Emacs 28 and the Master Branch, built on El Capitan, the issue is not present when using the test case:
(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 4600))
(string (prin1-to-string deep-object))
(result (read string)))
(when result
(message "Success!")))
I do not have any computers running a higher version of the MacOS operating system.
Keith
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> Date: [04-21-2022 06:33:29] <21 Apr 2022 15:33:29 +0200>
> From: Lars Ingebrigtsen <larsi@gnus.org>
> To: Keith David Bershatsky <esq@lawlist.com>
> Cc: Paul Eggert <eggert@cs.ucla.edu>, mail@vasilij.de, npostavs@gmail.com, 27779@debbugs.gnu.org
> Subject: Re: bug#27779: 26.0.50: read -- Re-entering top level after C stack overflow
>
> Keith David Bershatsky <esq@lawlist.com> writes:
>
> > TEST: Lanched without the terminal by opening Emacs.app.
> >
> > RESULT: Re-entering top level after C stack overflow
>
> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
>
> I've tried reproducing this issue, but with the test cases in the final
> message here, I get "Success" in the current Emacs.
>
> Are you still seeing this issue in recent Emacs versions?
next prev parent reply other threads:[~2022-04-21 18:56 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
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 [this message]
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=m21qxqmfj0.wl%esq@lawlist.com \
--to=esq@lawlist.com \
--cc=27779@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=larsi@gnus.org \
--cc=mail@vasilij.de \
--cc=npostavs@gmail.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).