From mboxrd@z Thu Jan 1 00:00:00 1970
Path: news.gmane.org!.POSTED!not-for-mail
From: Philipp Stephani
Newsgroups: gmane.emacs.devel
Subject: How much do we care about undefined behavior triggered by invalid
bytecode?
Date: Tue, 22 May 2018 15:31:31 +0200
Message-ID:
NNTP-Posting-Host: blaine.gmane.org
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="000000000000542207056ccb7031"
X-Trace: blaine.gmane.org 1526995794 22203 195.159.176.226 (22 May 2018 13:29:54 GMT)
X-Complaints-To: usenet@blaine.gmane.org
NNTP-Posting-Date: Tue, 22 May 2018 13:29:54 +0000 (UTC)
To: Emacs developers
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 22 15:29:49 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 1fL7MJ-0005bi-0j
for ged-emacs-devel@m.gmane.org; Tue, 22 May 2018 15:29:47 +0200
Original-Received: from localhost ([::1]:55791 helo=lists.gnu.org)
by lists.gnu.org with esmtp (Exim 4.71)
(envelope-from )
id 1fL7ON-0001WA-NZ
for ged-emacs-devel@m.gmane.org; Tue, 22 May 2018 09:31:55 -0400
Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57586)
by lists.gnu.org with esmtp (Exim 4.71)
(envelope-from ) id 1fL7OC-0001VK-HE
for emacs-devel@gnu.org; Tue, 22 May 2018 09:31:50 -0400
Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
(envelope-from ) id 1fL7OB-00057F-NH
for emacs-devel@gnu.org; Tue, 22 May 2018 09:31:44 -0400
Original-Received: from mail-oi0-x236.google.com ([2607:f8b0:4003:c06::236]:34406)
by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
(Exim 4.71) (envelope-from )
id 1fL7OB-00056x-In
for emacs-devel@gnu.org; Tue, 22 May 2018 09:31:43 -0400
Original-Received: by mail-oi0-x236.google.com with SMTP id l1-v6so16205611oii.1
for ; Tue, 22 May 2018 06:31:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:from:date:message-id:subject:to;
bh=AMnoox70dfNlDmH6yb9TYLLecnloQhsWA6b84mEArR0=;
b=GNrUVEkmHPGYTLgsHbfN2OJzW5qRj4lC7BgDJabrz//19imKrdF5lwFOSuNN9hmnk1
JWKqnxhoIHoODpBtuT/++Uw72Q3Z9ND/54Ku7tAMFaB3NMREySOagUZjxVAemXvPbXl1
K3AAogHSHwNKjjEora5Om2ogxGt6fJ7anN5/BTEuRX9WN0wvYpSk30UwsLDbZbdkBg7T
6hFXbVYHlT9SqZXP0ToLDzJnHfyu7chtJFFJKPMs5RDseIvcoHhtJzU+RrUSZ7ZBGqZD
r5D+RGqsmRfxKH3RdGxQTDfmmK9dAd6zyTwmU+/1xssQbF4I0gamj0hsLdMmSFLINEWL
+VFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=AMnoox70dfNlDmH6yb9TYLLecnloQhsWA6b84mEArR0=;
b=LHcmll7LWe3ZGUGKCtjtyAweIxe6Gz/EsS2QSRkDK8pbq4wJyKU6JkiMJmM9VFBlIC
cLNBfDNUqZjbavUXODByrbq+1HzhP50aspJc9U5sMFV7xdxe17OLmPlOx9aOASKX0XP+
G5jpEE7yeoXPXaxhvE78XpFNQZ2jghjQw5U4GBTebE9WERkDyYsBU3d15WuOeeqrMoOE
hr499TGvJ+OERJT5ryoTBhng4nS94YRzy4v7X1dZEuG3BuM3jaqRaj5VOhzGtSRB/MW8
G+m5dsntqWdwN0onk72+C87GpaReOl2VC+B8wfDclbLxc9V28eCh/j5U6Y5TFuK4nJNo
/heA==
X-Gm-Message-State: ALKqPwdzOPiCTX4HdETMq5FLEwYi9qi3U0GPt0SCQPv5/Ik10ZpHEAoI
wGT6iEJ1KjE3u0EOZtuZfEdj68aWZbyYv37irgKQGg==
X-Google-Smtp-Source: AB8JxZpAljzVYm2P3ytvH7X22JdyIXr79POAAqWOGeH1QbwHlo6x11aPMsjak3Q2+qEdKXRzCvK3gGJiwK0Jx7LHN9Q=
X-Received: by 2002:aca:1c9:: with SMTP id
192-v6mr14399710oib.175.1526995902274;
Tue, 22 May 2018 06:31:42 -0700 (PDT)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
recognized.
X-Received-From: 2607:f8b0:4003:c06::236
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:225550
Archived-At:
--000000000000542207056ccb7031
Content-Type: text/plain; charset="UTF-8"
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?
--000000000000542207056ccb7031
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
It's pretty easy to find examples of (printed represen=
tations of) invalid bytecode that trigger C-level assertions or undefined b=
ehavior ("crashes"). Should these be reported as bugs, or do we a=
ssume that any bytecode object is valid?
--000000000000542207056ccb7031--