From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Finding the dump Date: Sun, 27 Jan 2019 05:44:59 -0500 Message-ID: References: <83munr8jb1.fsf@gnu.org> <838szb8ey9.fsf@gnu.org> <83d0oj62bc.fsf@gnu.org> <87ef8z4g1m.fsf@igel.home> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="171273"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 27 11:45:58 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gnhwr-000iOU-1B for ged-emacs-devel@m.gmane.org; Sun, 27 Jan 2019 11:45:57 +0100 Original-Received: from localhost ([127.0.0.1]:43815 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gnhwp-00011F-W5 for ged-emacs-devel@m.gmane.org; Sun, 27 Jan 2019 05:45:56 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:39683) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gnhw0-00010Q-KD for emacs-devel@gnu.org; Sun, 27 Jan 2019 05:45:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gnhvz-0002eG-Li for emacs-devel@gnu.org; Sun, 27 Jan 2019 05:45:04 -0500 Original-Received: from smtp-as-02-09.vtxnet.net ([194.38.175.148]:36443 helo=smtp-as-02.vtxnet.net) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gnhvz-0002d2-FL for emacs-devel@gnu.org; Sun, 27 Jan 2019 05:45:03 -0500 Original-Received: from smtp-pri-03.vtx.ch (smtp-pri-03.vtxnet.net [212.147.62.137]) by smtp-as-02.vtxnet.net (Postfix) with ESMTP id 278CE41958; Sun, 27 Jan 2019 11:45:00 +0100 (CET) Original-Received: from fmsmemgm.homelinux.net (dyn.144-85-140-015.dsl.vtx.ch [144.85.140.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp-pri-03.vtx.ch (VTX Services SA) with ESMTPS id C139D1BF544; Sun, 27 Jan 2019 11:44:59 +0100 (CET) Original-Received: by fmsmemgm.homelinux.net (Postfix, from userid 20848) id 60E15AE10E; Sun, 27 Jan 2019 05:44:59 -0500 (EST) In-Reply-To: (Andreas Schwab's message of "Sun, 27 Jan 2019 11:32:57 +0100") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 194.38.175.148 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:232718 Archived-At: >> Given that there can be several dumps for a given `emacs` executable, >> I think it would make a lot of sense to try and support the creation of >> executable dumps (e.g. with a shebang which only needs to look for the >> one-and-only corresponding `emacs` executable regardless of argv[0]). > > I think the best option would be to add the fingerprint to name of the > dump file. That way the dump file would have a fixed name, independent > of how the corresponding emacs binaries is named, or how it is called. > It would just try to load emacs-${fingerprint}.pdmp, and always find the > right one. That prevents having several dumps for the same executable and that doesn't help finding the directory in which the dump is stored. I agree we should add the fingerprint, but I think it should be added to the `emacs` executable (so the executable-dump can easily find it). Stefan