all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 34707@debbugs.gnu.org, rms@gnu.org
Subject: bug#34707: Failure to find the associated pdump file
Date: Mon, 17 Jun 2019 22:23:02 +0300	[thread overview]
Message-ID: <83d0jct3s9.fsf@gnu.org> (raw)
In-Reply-To: <m3fto8ca7m.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon,  17 Jun 2019 20:56:13 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Mon, 17 Jun 2019 20:56:13 +0200
> Cc: 34707@debbugs.gnu.org
> 
> When Emacs is able to find the rest of itself, it's odd that it's
> not finding the pdump file, surely?

It's odd only if you don't consider the details.  Emacs finds the rest
of itself by consing Lisp strings, but that technique is unusable when
looking for the pdump file, because we must find it before we can
allocate memory etc., so we could set the heap flags correctly.  See
the comments in 'main'.  It's a typical bootstrap problem.

Solution is surely possible, it's just that it isn't "more of the
same", i.e. we cannot simply reuse the code which finds, say,
data-directory and similar.





  reply	other threads:[~2019-06-17 19:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02  3:27 bug#34707: Failure to find the associated pdump file Richard Stallman
2019-03-02  7:11 ` Eli Zaretskii
2019-03-03  2:58   ` Richard Stallman
2019-03-03  3:45     ` Eli Zaretskii
2019-03-04  3:28       ` Richard Stallman
2019-03-03  2:58   ` Richard Stallman
2019-03-03  3:41     ` Eli Zaretskii
2019-03-03 17:08       ` Eli Zaretskii
2019-03-04  3:26       ` Richard Stallman
2019-03-04  3:36         ` Eli Zaretskii
2019-03-03 17:06     ` Eli Zaretskii
2019-06-17 18:56 ` Lars Ingebrigtsen
2019-06-17 19:23   ` Eli Zaretskii [this message]
2019-06-18  3:07   ` Richard Stallman
2019-06-28  6:42     ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83d0jct3s9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34707@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=rms@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.