[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to make aot native-compilation and pdmp creation reproduceable
From: |
Gerd Möllmann |
Subject: |
Re: How to make aot native-compilation and pdmp creation reproduceable |
Date: |
Mon, 09 Oct 2023 07:47:46 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>
>> Björn Bidar <bjorn.bidar@thaodan.de> writes:
>>
>>>> Did you configure Emacs with --disable-build-details ?
>>>
>>> Yes it is.
>>
>> Hm, maybe addr2line could help here? I don't have that here (macOS), so
>> I can't try.
>
> Errr, the fingerprint is of course also stored in the executable...
>
> volatile unsigned char fingerprint[] = ...
>
> That could explain the difference.
Can you determine if x-win.eln gets dumped into the pdmp file? That
would explain the differences, and it would all boil down to the
print-circle thing.
Re: How to make aot native-compilation and pdmp creation reproduceable, Andrea Corallo, 2023/10/08
Re: How to make aot native-compilation and pdmp creation reproduceable, Eli Zaretskii, 2023/10/09