From: Alan J Third <alan@idiocy.org>
To: markus.triska@gmx.at
Cc: larsi@gnus.org, 2099@debbugs.gnu.org
Subject: bug#2099: 23.0.60; `mark_object' with larger nested objects crashes Emacs
Date: Mon, 11 Jan 2016 20:32:48 +0000 [thread overview]
Message-ID: <m2a8ob26xb.fsf@galloway.idiocy.org> (raw)
In-Reply-To: <trinity-00bb75b2-fb15-40c4-8cf4-ce91199cced6-1452542268915@3capp-gmx-bs61> (markus triska's message of "Mon, 11 Jan 2016 20:57:49 +0100")
markus.triska@gmx.at writes:
> I find it hard to believe that a way to crash Emacs is somehow *not*
> considered a bug. If that is the case, I agree with what Glenn recently
> said: Just deal with this report in any way you wish.
My thinking was simply that it sounds like it will require
reimplementation of the GC, and that's not likely to happen any time
soon, or perhaps ever.
Looking over the debbugs docs again, though, it should probably be
changed to wishlist, as Eli suggested originally. Like you say, a crash
is surely a bug, even if it is hard to fix.
FWIW I found a 'real-world' bug report, bug#16039, which appears to have
the same cause, although it requires a different remedy.
--
Alan Third
next prev parent reply other threads:[~2016-01-11 20:32 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2a8ob26xb.fsf@galloway.idiocy.org \
--to=alan@idiocy.org \
--cc=2099@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=markus.triska@gmx.at \
/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.