From: Eli Zaretskii <eliz@gnu.org>
To: markus.triska@gmx.at
Cc: alan@idiocy.org, 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 21:16:38 +0200 [thread overview]
Message-ID: <8337u4kju1.fsf@gnu.org> (raw)
In-Reply-To: <trinity-52670635-2f5d-40e0-9f7b-be0aa89cef05-1452539426201@3capp-gmx-bs16> (markus.triska@gmx.at)
> From: markus.triska@gmx.at
> Cc: "Eli Zaretskii" <eliz@gnu.org>, 2099@debbugs.gnu.org, larsi@gnus.org
> Date: Mon, 11 Jan 2016 20:10:26 +0100
>
> Marking this as "wontfix" seems particularly inapplicable to me: This
> shortcoming crashes Emacs and potentially causes data loss for users,
> not only in such an artificial test case but in other situations too.
> This shortcoming prevents my testing Emacs in many other ways that would
> help me to find and correct more shortcomings and make Emacs more robust.
Sorry, I don't understand: what testing? Can you describe the
real-life use case behind this bug report? The recipe as shown looks
like a deliberate way to cause Emacs to overflow its stack; surely,
that's not what you intended to test?
next prev parent reply other threads:[~2016-01-11 19:16 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 [this message]
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=8337u4kju1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=2099@debbugs.gnu.org \
--cc=alan@idiocy.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 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).