From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: 34180@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
Paul Eggert <eggert@cs.ucla.edu>, Eli Zaretskii <eliz@gnu.org>
Subject: bug#34180: 27.0.50; argv[0] used incorrectly to find the .pdmp
Date: Mon, 11 Oct 2021 20:51:31 -0400 [thread overview]
Message-ID: <jwv7dejrruo.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <97e17ac7-b46f-5cac-e0da-8a8f1e26813b@dancol.org> (Daniel Colascione's message of "Mon, 11 Oct 2021 13:13:18 -0700")
> 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.
Maybe we could avoid this problem by moving most of the Emacs executable
to a shared library, so the Emacs executable would be just a `dump`
variable and ` main` function which passes it to an entry point provided
by libemacs<fingerpring>.so`.
I'm not sure I like the idea of building a shared lib and the extra
complexity of making sure the Emacs executable finds it.
Stefan
next prev parent reply other threads:[~2021-10-12 0:51 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 [this message]
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=jwv7dejrruo.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=34180@debbugs.gnu.org \
--cc=dancol@dancol.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).