From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Noam Postavsky Newsgroups: gmane.emacs.devel Subject: Re: How much do we care about undefined behavior triggered by invalid bytecode? Date: Tue, 22 May 2018 09:42:38 -0400 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: blaine.gmane.org 1526996501 8534 195.159.176.226 (22 May 2018 13:41:41 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 22 May 2018 13:41:41 +0000 (UTC) Cc: Emacs developers To: Philipp Stephani Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 22 15:41:37 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fL7Xj-00025K-IF for ged-emacs-devel@m.gmane.org; Tue, 22 May 2018 15:41:35 +0200 Original-Received: from localhost ([::1]:55843 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fL7Zq-0006GT-PU for ged-emacs-devel@m.gmane.org; Tue, 22 May 2018 09:43:46 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60520) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fL7Ym-0005Xy-Gl for emacs-devel@gnu.org; Tue, 22 May 2018 09:42:41 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fL7Yl-00023t-Po for emacs-devel@gnu.org; Tue, 22 May 2018 09:42:40 -0400 Original-Received: from mail-ot0-x230.google.com ([2607:f8b0:4003:c0f::230]:40801) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fL7Yl-00023S-Ks for emacs-devel@gnu.org; Tue, 22 May 2018 09:42:39 -0400 Original-Received: by mail-ot0-x230.google.com with SMTP id n1-v6so20978064otf.7 for ; Tue, 22 May 2018 06:42:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dYJZCqOgCPLU9Ta2lT9L97aFOdL7gKuX6NtY+K8Yxr4=; b=EWBv7DeGQBqPSgDJ7yxOYK7K3CMOcshs8ALIGOtGH27rmvib6Zyrnpl6boFwmM00hG 0oJxKD2USN397xYB1Fp2W64k146IqTJugqTyBx7dsp1ZXW2hO/7xEngYSfft8rIF6SzN jFIiJAYWWeaC6/UOUxpcYfA2VkoxnDFkb1tmESoEPaGF4O0YC4RbbERZ9vUUeAaRe91k agWUNP+C0B9A7mDx5JOD55f+Qjk1RUDLC+/8d5A5cslEeSkDl/ubwVko7mwLSNJ5dH96 WtBHN1DRFuthyt4uEuimNl/Mu8sj5hqCHSFJWoPqqmeL7O0gRRlWep0Krkw72A0ctFFF DjXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dYJZCqOgCPLU9Ta2lT9L97aFOdL7gKuX6NtY+K8Yxr4=; b=WgjMIBU37hrBpiOXzgG2DyEHMzP5G8bhFji7raPZKsgwOiQkdVQh8+uw0oKbhMe914 4ifviCbXKQuLZtZQIUNNdnqMeigdI1Ca/jOR0CtXwy4cvOj1fzKxDl48ijwjEz0tjCWT 6Z0cMIm91Cl9P/Sp008n1V3+xg/n1WUaEi0sZ1ObCGxlfQ5+NAGCsLq1dcQ/++2/g6KI hOJcY30755oYpD6BUM/vyOXgn9/mHeOQZOtqnPwMtuqC1RL/SzIXajm5PncuMoNeLgyV g64l+6sS+4mFXUX+4171PfP63A80HvlLDhWqeeCrLWkiVBk2N4sWSkIE20/PUH69ayat 3hFg== X-Gm-Message-State: ALKqPwdcU2P0AkelltWcm2hTV5dUUUfNYob78L8DSCWKJDH6yhHryG+j mzCTInzMOI6nx2pAAgjgxIbAz/YyzVjc7I/UZ8Y= X-Google-Smtp-Source: AB8JxZoUR4O0Bs4TSvcwG18bLvtPrbKfzCsFzc+y4259t0MsYucbCjxKPn5PH9RW7JV5ZKV1m7Nch03Ll9GhpQv3DD0= X-Received: by 2002:a9d:501a:: with SMTP id a26-v6mr16977636oth.82.1526996558960; Tue, 22 May 2018 06:42:38 -0700 (PDT) Original-Received: by 10.74.5.135 with HTTP; Tue, 22 May 2018 06:42:38 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4003:c0f::230 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:225551 Archived-At: On 22 May 2018 at 09:31, Philipp Stephani 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).