From: Daniel Colascione <dancol@dancol.org>
To: Paul Eggert <eggert@cs.ucla.edu>,
Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Cc: 34180@debbugs.gnu.org, monnier@IRO.UMontreal.CA
Subject: bug#34180: 27.0.50; argv[0] used incorrectly to find the .pdmp
Date: Mon, 11 Oct 2021 13:13:18 -0700 [thread overview]
Message-ID: <97e17ac7-b46f-5cac-e0da-8a8f1e26813b@dancol.org> (raw)
In-Reply-To: <d30902b6-1c70-77c2-3a34-af73a2536af2@cs.ucla.edu>
On 10/11/21 8:10 AM, Paul Eggert wrote:
> On 10/11/21 7:02 AM, Lars Ingebrigtsen wrote:
>> It looks like find_executable from progreloc in gnulib provides a
>> portable interface for this?
>
> It does, although it drags in a bunch of other Gnulib modules, as this
> stuff is wildly system-dependent.
>
> For ordinary Emacs installation, I've long thought that a better
> approach is to store the default .pdmp file as a readonly char array
> within the Emacs executable itself. This would be easier for installers,
> sysadmins and users, as it would entail no funny rules about installing
> two files, keeping them in sync, symlinks, PATH, argv[0], relative
> names, security, etc.
It's not quite that simple though. The pdmp file includes offsets of
data structures within the Emacs executable. Rebuilding the executable
with a big char array will change these offsets and invalidate the pdmp
blob you're trying to embed. Now, you could try to guess the size of the
blob ahead of time, include a dummy embedded array of that size in
Emacs, dump, and then overwrite the embedded array post-build, but
there's no guarantee that doing that would actually work on all systems.
I'd rather get out of the business of mucking with executable files even
if it means we have a bit of extra complexity arising from having to
deal with out-of-band pdmp files.
next prev parent reply other threads:[~2021-10-11 20:13 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 [this message]
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
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=97e17ac7-b46f-5cac-e0da-8a8f1e26813b@dancol.org \
--to=dancol@dancol.org \
--cc=34180@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--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).