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 14:27:59 +0200 [thread overview]
Message-ID: <59495BCF-EF2F-4E1F-A466-1CC61CE57893@acm.org> (raw)
In-Reply-To: <jwv7eev2w88.fsf@iro.umontreal.ca>
I don't think Paul meant that we necessarily have to use the embedded dump in-place. It could just as well be the source of a memory copy to its runtime location; everything would then work just like today except that the dump file is embedded into the executable.
Basically, regenerating the dump file means relinking the executable and that's it, no mucking about with executables required. It is easy to write a portable solution that works everywhere.
next prev parent reply other threads:[~2021-10-12 12:27 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 [this message]
2021-10-12 16:24 ` Daniel Colascione
2021-10-12 16:46 ` Eli Zaretskii
2021-10-12 16:59 ` Mattias Engdegård
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=59495BCF-EF2F-4E1F-A466-1CC61CE57893@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).