From: Philipp Stephani <p.stephani2@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Noam Postavsky <npostavs@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: How much do we care about undefined behavior triggered by invalid bytecode?
Date: Tue, 22 May 2018 17:37:27 +0200 [thread overview]
Message-ID: <CAArVCkR0DuvE2f9qXqR7r5i8PA9478VDwW6-YuqhzDKqpo4EBg@mail.gmail.com> (raw)
In-Reply-To: <2f400c58-1214-d442-f3a9-30b5c7d73863@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
Paul Eggert <eggert@cs.ucla.edu> schrieb am Di., 22. Mai 2018 um 16:51 Uhr:
> Noam Postavsky wrote:
> > Oh, you meant just reading the object causes a crash?
>
> I doubt he meant that. Surely he meant that if you read and then execute a
> bytecode object, you can easily crash Emacs.
>
>
No, I did mean "read." For example, the following triggers an assertion:
emacs -Q -batch -eval '(let ((load-force-doc-strings t)) (read "#[0
\"\"]"))'
./lisp.h:1723: Emacs fatal error: assertion failed: 0 <= idx && idx < ASIZE
(array)
Fatal error 6: Abort trapAbort trap: 6
[-- Attachment #2: Type: text/html, Size: 1167 bytes --]
next prev parent reply other threads:[~2018-05-22 15:37 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
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 [this message]
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=CAArVCkR0DuvE2f9qXqR7r5i8PA9478VDwW6-YuqhzDKqpo4EBg@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=npostavs@gmail.com \
/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).