Re: How much do we care about undefined behavior triggered by invalid bytecode?

[Andreas Schwab]

On Mai 22 2018, Noam Postavsky <address@hidden> wrote:

> On 22 May 2018 at 09:31, Philipp Stephani <address@hidden> 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).

Nevertheless, IMHO the bytecode interpreter should be made robust where
possible.

Andreas.

-- 
Andreas Schwab, SUSE Labs, address@hidden
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."