From: Richard Stallman <rms@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: p.stephani2@gmail.com, npostavs@gmail.com, emacs-devel@gnu.org
Subject: Re: How much do we care about undefined behavior triggered by invalid bytecode?
Date: Tue, 22 May 2018 23:28:06 -0400 [thread overview]
Message-ID: <E1fLKRa-0007Xv-9K@fencepost.gnu.org> (raw)
In-Reply-To: <mvmzi0rpz5g.fsf@suse.de> (message from Andreas Schwab on Tue, 22 May 2018 16:01:47 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> Nevertheless, IMHO the bytecode interpreter should be made robust where
> possible.
I think it would be an improvement to do check for nonsensical
bytecode when creating a bytecode object. As long as it doesn't make
reading a compiled file much slower.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2018-05-23 3:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 13:31 How much do we care about undefined behavior triggered by invalid bytecode? Philipp Stephani
2018-05-22 13:42 ` Noam Postavsky
2018-05-22 14:01 ` Andreas Schwab
2018-05-23 3:28 ` Richard Stallman [this message]
2018-05-22 14:04 ` Philipp Stephani
2018-05-22 14:40 ` Noam Postavsky
2018-05-22 14:51 ` Paul Eggert
2018-05-22 15:37 ` Philipp Stephani
2018-05-25 0:30 ` Tom Tromey
2018-05-22 17:30 ` Philipp Stephani
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=E1fLKRa-0007Xv-9K@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=npostavs@gmail.com \
--cc=p.stephani2@gmail.com \
--cc=schwab@suse.de \
/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).