From: Noam Postavsky <npostavs@gmail.com>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 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 09:42:38 -0400 [thread overview]
Message-ID: <CAM-tV-885iDAPxgXbKgrn77Md6RvCJEq2poYW1k3QiT1=T_wVw@mail.gmail.com> (raw)
In-Reply-To: <CAArVCkT2=V9P5UW1+CEDLEiQY_7ND5V3EoAD=3VZ8OM2TgSn1Q@mail.gmail.com>
On 22 May 2018 at 09:31, Philipp Stephani <p.stephani2@gmail.com> wrote:
> 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?
The latter, according to the manual (elisp) Byte-Code Objects:
You should not try to come up with the elements for a byte-code
function yourself, because if they are inconsistent, Emacs may crash
when you call the function. Always leave it to the byte compiler to
create these objects; it makes the elements consistent (we hope).
next prev parent reply other threads:[~2018-05-22 13:42 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM-tV-885iDAPxgXbKgrn77Md6RvCJEq2poYW1k3QiT1=T_wVw@mail.gmail.com' \
--to=npostavs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@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 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.