From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#47067: 28.0.50; [feature/native-comp] Crash while scrolling through dispnew.c Date: Sun, 21 Mar 2021 16:41:14 +0000 Message-ID: References: <83sg52lykn.fsf@gnu.org> <835z1wl6ao.fsf@gnu.org> <83zgz8jq7t.fsf@gnu.org> <83pn04jhge.fsf@gnu.org> <838s6rjvup.fsf@gnu.org> <83pmzve442.fsf@gnu.org> <83ft0rdyld.fsf@gnu.org> <83mtuycft5.fsf@gnu.org> <83r1k8bzqs.fsf@gnu.org> <83k0q0bu05.fsf@gnu.org> <83eeg8bjvj.fsf@gnu.org> <83a6qwbiyd.fsf@gnu.org> Reply-To: Andrea Corallo Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39778"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: 47067@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Mar 21 17:42:18 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lO19c-000AE2-UT for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 21 Mar 2021 17:42:16 +0100 Original-Received: from localhost ([::1]:53384 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lO19b-0007l2-VJ for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 21 Mar 2021 12:42:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50090) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lO19P-0007ke-1m for bug-gnu-emacs@gnu.org; Sun, 21 Mar 2021 12:42:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:43793) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lO19O-0006QD-D7 for bug-gnu-emacs@gnu.org; Sun, 21 Mar 2021 12:42:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lO19O-0007xC-Af for bug-gnu-emacs@gnu.org; Sun, 21 Mar 2021 12:42:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Andrea Corallo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 21 Mar 2021 16:42:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 47067 X-GNU-PR-Package: emacs Original-Received: via spool by 47067-submit@debbugs.gnu.org id=B47067.161634487730521 (code B ref 47067); Sun, 21 Mar 2021 16:42:02 +0000 Original-Received: (at 47067) by debbugs.gnu.org; 21 Mar 2021 16:41:17 +0000 Original-Received: from localhost ([127.0.0.1]:55339 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lO18f-0007wC-5b for submit@debbugs.gnu.org; Sun, 21 Mar 2021 12:41:17 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:51781) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lO18d-0007w4-VW for 47067@debbugs.gnu.org; Sun, 21 Mar 2021 12:41:16 -0400 Original-Received: from mab (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 12LGfEgW000674 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Sun, 21 Mar 2021 16:41:14 GMT In-Reply-To: <83a6qwbiyd.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 21 Mar 2021 17:54:50 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:202787 Archived-At: Eli Zaretskii writes: >> From: Andrea Corallo >> Cc: 47067@debbugs.gnu.org >> Date: Sun, 21 Mar 2021 15:41:48 +0000 >> >> I was thinking, the only downside I see of this solution is that while >> we can tweak the build system to signal to Emacs that a certain file >> being compiled will be used for dump, this will indeed not be possible >> for subsequent dumps. > > I don't think I follow: why would this be impossible for subsequent > dumps? > > Maybe I should describe the use case this is supposed to solve. > Imagine a repository where Emacs is being built regularly, and where > old Emacs builds are kept for long periods of time, together with > their *.pdmp files. So we will have emacs-28.0.50.1, emacs-28.0.50.2, > ... emacs-28-0.50.1000, ..., and their respective *.pdmp files. The > intent is to be able to run these old binaries for quick "bisecting" > of issues reported by users. This is what I do on my system: I keep > one build from each of the previous months, and delete the rest. > > Until native-comp, keeping the binary and the .pdmp file was enough > for being able to run that binary. With native-comp, we also need the > *.eln files that were dumped into each of the *.pdmp files. I'm > trying to find a reasonable solution to this problem. Thanks I think I've understood the case. I was referring to a different case, future dumps done by the user calling directly `dump-emacs-portable', in that case some .eln might stay where they were placed originally (not in the preloaded subfolder). I know for now we don't support officially `dump-emacs-portable' to be used directly by the user, so I'm not sure that's a real issue, but I was trying to think future proof. Thanks Andrea