From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: 2099@debbugs.gnu.org
Subject: bug#2099: 23.0.60; `mark_object' with larger nested objects crashes Emacs
Date: Mon, 12 Sep 2011 01:47:42 +0200 [thread overview]
Message-ID: <m3sjo2ej4x.fsf@stories.gnus.org> (raw)
In-Reply-To: <20090128230645.07F1DC468CC@mt-computer.local>
So, the problem here seems simply to be that we blow up the stack by
recursing so ridiculously deep? I think?
Looking at mark_object, it seems like it could pretty easily be
rewritten to be non-recursive, just by changing it into a loop, and
using a stack to do visit all the objects.
But that's probably not an Emacs 24.1 thing.
The other question is what other interesting deep-nesting bugs a
structure like that might reveal, so even if we fix the mark_object
case, that might not help us much. Difficult to say...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-09-11 23:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 23:06 bug#2099: 23.0.60; `mark_object' with larger nested objects crashes Emacs Markus Triska
2011-09-11 21:08 ` Lars Magne Ingebrigtsen
2011-09-11 21:54 ` Andreas Schwab
2011-09-11 21:53 ` Lars Magne Ingebrigtsen
2011-09-11 23:47 ` Lars Magne Ingebrigtsen [this message]
2016-01-10 22:12 ` Alan J Third
2016-01-11 15:11 ` Eli Zaretskii
2016-01-11 17:49 ` Alan J Third
2016-01-11 19:10 ` markus.triska
2016-01-11 19:16 ` Eli Zaretskii
2016-01-11 19:57 ` markus.triska
2016-01-11 20:32 ` Alan J Third
2016-01-11 20:45 ` Eli Zaretskii
2016-01-11 20:32 ` Eli Zaretskii
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=m3sjo2ej4x.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=2099@debbugs.gnu.org \
/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).