unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: Size of emacs.pdmp changes between successive installs
Date: Wed, 20 Nov 2019 00:21:45 +0100	[thread overview]
Message-ID: <w6geey3laeu.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <871ru34tq0.fsf@igel.home> (Andreas Schwab's message of "Tue, 19 Nov 2019 19:16:39 +0100")

>>>>> On Tue, 19 Nov 2019, Andreas Schwab wrote:

> On Nov 19 2019, Ulrich Mueller wrote:
>> For two successive installs from a clean checkout of the same git
>> commit, emacs.pdmp ends up having slightly different size:
>>
>> $ stat -c %s /usr/libexec/emacs/27.0.50/x86_64-pc-linux-gnu/emacs.pdmp
>> 10563744
>>
>> $ stat -c %s /usr/libexec/emacs/27.0.50/x86_64-pc-linux-gnu/emacs.pdmp
>> 10563728
>>
>> Why is that so? Shouldn't it be deterministic?

> Try disabling ASLR.  That doesn't make it completely reproducible,
> though.

Indeed. After doing "echo -n 0 >/proc/sys/kernel/randomize_va_space"
I get at least the same size every time.

This is with Linux 4.14.154 and glibc 2.30.



      parent reply	other threads:[~2019-11-19 23:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 16:59 Size of emacs.pdmp changes between successive installs Ulrich Mueller
2019-11-19 17:18 ` Paul Eggert
2019-11-19 17:45 ` Eli Zaretskii
2019-11-19 18:19   ` Andreas Schwab
2019-11-19 18:16 ` Andreas Schwab
2019-11-19 20:56   ` Paul Eggert
2019-11-19 22:14     ` Andreas Schwab
2019-11-19 23:45       ` Ulrich Mueller
2019-11-20  2:27         ` Paul Eggert
2019-11-20 11:55           ` Andreas Schwab
2019-11-20 19:54             ` Paul Eggert
2019-11-20 19:59               ` Paul Eggert
2019-11-20  9:29         ` Andreas Schwab
2019-11-20 11:42           ` Ulrich Mueller
2019-11-19 23:21   ` Ulrich Mueller [this message]

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=w6geey3laeu.fsf@kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.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 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).