From: Philipp Stephani <p.stephani2@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: How much do we care about undefined behavior triggered by invalid bytecode?
Date: Tue, 22 May 2018 15:31:31 +0200 [thread overview]
Message-ID: <CAArVCkT2=V9P5UW1+CEDLEiQY_7ND5V3EoAD=3VZ8OM2TgSn1Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 235 bytes --]
It's pretty easy to find examples of (printed representations of) invalid
bytecode that trigger C-level assertions or undefined behavior ("crashes").
Should these be reported as bugs, or do we assume that any bytecode object
is valid?
[-- Attachment #2: Type: text/html, Size: 271 bytes --]
next reply other threads:[~2018-05-22 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 13:31 Philipp Stephani [this message]
2018-05-22 13:42 ` How much do we care about undefined behavior triggered by invalid bytecode? Noam Postavsky
2018-05-22 14:01 ` Andreas Schwab
2018-05-23 3:28 ` Richard Stallman
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='CAArVCkT2=V9P5UW1+CEDLEiQY_7ND5V3EoAD=3VZ8OM2TgSn1Q@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=emacs-devel@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).