From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Noam Postavsky Newsgroups: gmane.emacs.bugs Subject: bug#31549: 25.3; bytecompile fails with eval-when-compile Date: Sun, 27 May 2018 11:09:48 -0400 Message-ID: <87sh6ddtj7.fsf@gmail.com> References: <8636yknjy1.fsf@gmail.com> <87sh6jgtao.fsf@gmail.com> <83po1mcsty.fsf@gnu.org> <87k1rugfxd.fsf@gmail.com> <83fu2hatxv.fsf@gnu.org> <87603chhwm.fsf@gmail.com> <83r2m09s0o.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1527433700 4881 195.159.176.226 (27 May 2018 15:08:20 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 27 May 2018 15:08:20 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) Cc: ynyaaa@gmail.com, 31549@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun May 27 17:08:15 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1fMxHK-0001Ae-7p for geb-bug-gnu-emacs@m.gmane.org; Sun, 27 May 2018 17:08:14 +0200 Original-Received: from localhost ([::1]:52371 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fMxJR-0002Gl-C4 for geb-bug-gnu-emacs@m.gmane.org; Sun, 27 May 2018 11:10:25 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37307) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fMxJ8-0002AY-5u for bug-gnu-emacs@gnu.org; Sun, 27 May 2018 11:10:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fMxJ4-00026Y-U0 for bug-gnu-emacs@gnu.org; Sun, 27 May 2018 11:10:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:43169) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fMxJ4-00026S-QQ for bug-gnu-emacs@gnu.org; Sun, 27 May 2018 11:10:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fMxJ4-0006Pz-Ev for bug-gnu-emacs@gnu.org; Sun, 27 May 2018 11:10:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Noam Postavsky Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 27 May 2018 15:10:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 31549 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 31549-submit@debbugs.gnu.org id=B31549.152743379924657 (code B ref 31549); Sun, 27 May 2018 15:10:02 +0000 Original-Received: (at 31549) by debbugs.gnu.org; 27 May 2018 15:09:59 +0000 Original-Received: from localhost ([127.0.0.1]:51066 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fMxJ0-0006PY-SC for submit@debbugs.gnu.org; Sun, 27 May 2018 11:09:59 -0400 Original-Received: from mail-it0-f43.google.com ([209.85.214.43]:40751) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fMxIy-0006PG-Oa; Sun, 27 May 2018 11:09:57 -0400 Original-Received: by mail-it0-f43.google.com with SMTP id j186-v6so12133776ita.5; Sun, 27 May 2018 08:09:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=/pyxpd8dtscxQVQeXVuNsKPq6QKl82qRNbHv2GjHwvQ=; b=eExkzX309J4R8/DdcazJUARJ4mBrWZ4hcaLjTQ2Hu61FktVI4lHpmvse6rWTzZFDU1 76Ve7rk8+eXRQemYCCgcK+y/6DXbZdGlQ3VIx6MWzqp5FKkcFbX53GgCtlhAeN+HyR+1 +s37CsGJN9Uuk1NlGO/O1VKYs6lBofwc3TEv7aRfcdDw8fuKyMQLzxKWvNptS2dhZKlu gEu9/drjKWxMjvrIIkZYwDkR1mP13u9denaH9E5Ce1wbHmCtTpudFvn/9UTr0VeF05Vv bDXP27dOi6NuIq3JeG+8ZhEMOLN9DLnujwpXlilS5Fc6Q6gzrN2p05jUpiL1GkOwwt5M 9C4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=/pyxpd8dtscxQVQeXVuNsKPq6QKl82qRNbHv2GjHwvQ=; b=jpYa1LNng39v5qFiQvqcAk4xGkqjks5b3vUIPeV7fR0XBk0U24qM2HAyKthHyploBC 5voC5nNGwygosave35BMV8dTWYEZb+ChkmSzgZSAvH1jHqmNqcAkqQ03EViBt9lXl8Mt cWBlSthsOIdyFCMmHjvab3dIdGAmY0zulIapbwYqkOy5kPP7Pt1nNLZT4UCudqbI57zr TKFHij/CVXxQMvnhExy+VYN/ag7c9sVcKpvewODMZr3QJ66ewAaB3ULiC/Ax1AzEruZS n51yYl4BTDLBEIsrp7zvadkMNsRzugmHHkacXRtxpKX8C6pI18b/LQ9gutQ1tYxibnhW mR0g== X-Gm-Message-State: ALKqPwd9BBSN1eGOkhM0Uxg56CgIJJp7/1Xq02c6uzqQtlgqRy1dvHX9 VOWA0hZi86/2QemVsi8K8nto7w== X-Google-Smtp-Source: ADUXVKLrL6Y38L42DslppOR3u5Jyploon3/WG+vYnZCZOEQ2KwBnwMzsOsK+7GVCwp26PMVz34H86A== X-Received: by 2002:a24:3989:: with SMTP id l131-v6mr8757682ita.28.1527433790946; Sun, 27 May 2018 08:09:50 -0700 (PDT) Original-Received: from zebian (cbl-45-2-119-34.yyz.frontiernetworks.ca. [45.2.119.34]) by smtp.googlemail.com with ESMTPSA id e15-v6sm15161217ioc.54.2018.05.27.08.09.49 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 27 May 2018 08:09:49 -0700 (PDT) In-Reply-To: <83r2m09s0o.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 25 May 2018 09:19:19 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:146591 Archived-At: close 31549 quit Eli Zaretskii writes: >> From: Noam Postavsky >> Cc: ynyaaa@gmail.com, 31549@debbugs.gnu.org >> Date: Thu, 24 May 2018 17:18:17 -0400 >> >> Sorry, if my initial response confused things > > Seeking the truth doesn't always work in linear ways ;-) > >> I'm fairly certain now that there is no way to trigger this error by >> compiling a Lisp program in Emacs 26. It would have to require a >> stack depth of 2^63 (or 2^31 on 32 bit builds), I imagine actual >> memory exhaustion would happen first. >> >> Actually, even though memory_full probably isn't correct, maybe we >> should just leave it. Triggering this error probably indicates some bug >> in Emacs, so the first thing to do after hitting it would be to set a >> breakpoint in gdb; this is a bit more convenient to do with memory_full >> than Fsignal or error: fewer false positives. > > Fine by me, but do we understand what change(s) between 25.3 and 26.1 > fixed this problem? If not, maybe we should try to understand that? Ah, here it is, seems pretty straightforward. [1: cb71a119f7]: 2016-08-09 01:31:22 -0700 Remove arbitrary limit on bytecode maxdepth https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=cb71a119f7231984e010cc28ef33854721036a0f