From: "Mattias Engdegård" <mattiase@acm.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: 34180@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
Paul Eggert <eggert@cs.ucla.edu>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#34180: 27.0.50; argv[0] used incorrectly to find the .pdmp
Date: Tue, 12 Oct 2021 18:59:43 +0200 [thread overview]
Message-ID: <E7B027C0-5D0E-4E19-9CC6-2AF3BC7CFAFB@acm.org> (raw)
In-Reply-To: <3b65b08e-4f6d-d2cb-6621-7f6e988227de@dancol.org>
> Copying the dump on startup will hurt performance --- the dump is meant to be used directly from a disk-backed file.
Is the cost of the all-sequential) paging-in noticeable? Surely a fair part of it will be required more or less immediately anyway.
The worst-case cost of an empty `-batch -Q` run actually decreased somewhat when forcing the dump to be read up front, although admittedly that was from a hot cache.
> relinking the executable can change all the locations of the symbols in the binary, and if symbol locations change, any previously-generated dump becomes invalid.
Partial linking would help, unless we use a diabolic linker that rearranges the symbols based on the contents of a data array.
> Even if on *some* platforms *today* we can replace an embedded dump image in an already-built executable without re-linking the thing, there's no guarantee that we can continue doing that.
No, I don't think that's a viable way. As you say, in-place modification wrecks havoc with any sort of binary checksumming.
prev parent reply other threads:[~2021-10-12 16:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 16:07 bug#34180: 27.0.50; argv[0] used incorrectly to find the .pdmp Stefan Monnier
2019-01-27 3:54 ` Daniel Colascione
2019-01-27 15:23 ` Eli Zaretskii
2021-10-11 14:02 ` Lars Ingebrigtsen
2021-10-11 14:04 ` Lars Ingebrigtsen
2021-10-11 15:10 ` Paul Eggert
2021-10-11 16:05 ` Eli Zaretskii
2021-10-11 20:13 ` Daniel Colascione
2021-10-12 0:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-12 10:51 ` Lars Ingebrigtsen
2021-10-12 11:54 ` Philipp Stephani
2021-10-12 11:59 ` Lars Ingebrigtsen
2021-10-12 14:10 ` Eli Zaretskii
2021-10-11 15:54 ` Eli Zaretskii
2021-10-12 10:48 ` Lars Ingebrigtsen
2021-10-11 21:16 ` Richard Stallman
2021-10-12 12:27 ` Mattias Engdegård
2021-10-12 16:24 ` Daniel Colascione
2021-10-12 16:46 ` Eli Zaretskii
2021-10-12 16:59 ` Mattias Engdegård [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E7B027C0-5D0E-4E19-9CC6-2AF3BC7CFAFB@acm.org \
--to=mattiase@acm.org \
--cc=34180@debbugs.gnu.org \
--cc=dancol@dancol.org \
--cc=eggert@cs.ucla.edu \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).