From: Stefan Monnier <monnier@iro.umontreal.ca>
To: rrandresf@gmail.com (Andrés Ramírez)
Cc: 14120@debbugs.gnu.org
Subject: bug#14120: invalid load-history in emacsen that CANNOT_DUMP
Date: Mon, 17 Feb 2020 10:09:59 -0500 [thread overview]
Message-ID: <jwvv9o5jlqz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <861rqtjq10.fsf@gmail.com> ("Andrés Ramírez"'s message of "Mon, 17 Feb 2020 13:34:51 +0000")
>> FWIW, CANNOT_DUMP is a compilation option that is only meant to be used
>> as a temporary measure. It suffers from various shortcomings (other
>> than the obvious startup cost).
>
>> So before we start trying to fix them, I'd like to know why you need to
>> use CANNOT_DUMP.
>
> I use CANNOT_DUMP on a daily basis on emacs 23.4 (the best emacs for
> poor machines. it renders very quick. I would like to profile It against
> latest emacs which I also use) It was compiled on on November 13 2019. I have suffered
> the same issue as Templeton.
Any chance you can try and investigate where/why/how that spurious value gets
pushed to `load-history`?
AFAICT the only place where `load-history` gets modified is in
lread.c:build_load_history.
Could you add some assertions there to try and catch the sucker?
Stefan
next prev parent reply other threads:[~2020-02-17 15:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 22:47 bug#14120: invalid load-history in emacsen that CANNOT_DUMP BT Templeton
2013-04-03 18:29 ` Stefan Monnier
2019-09-06 0:09 ` Glenn Morris
2020-02-17 13:34 ` Andrés Ramírez
2020-02-17 15:09 ` Stefan Monnier [this message]
2020-02-17 17:14 ` andrés ramírez
2020-02-17 17:46 ` Stefan Monnier
2020-02-18 1:01 ` andrés ramírez
2020-02-18 1:34 ` andrés ramírez
2020-02-18 13:40 ` Stefan Monnier
2020-02-18 13:50 ` andrés ramírez
2020-02-16 20:55 ` bug#14120: [Robert Weiner] Emacs history selection non-string arguments causing failures for a long time Stefan Monnier
2020-02-17 1:52 ` Stefan Monnier
2020-02-17 2:22 ` Robert Weiner
2020-02-17 3:18 ` Glenn Morris
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=jwvv9o5jlqz.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=14120@debbugs.gnu.org \
--cc=rrandresf@gmail.com \
/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).