[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: pdumping "into" the executable
From: |
Clément Pit-Claudel |
Subject: |
Re: pdumping "into" the executable |
Date: |
Mon, 26 Feb 2018 17:34:11 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 |
On 2018-02-26 16:10, Tom Tromey wrote:
> Maybe instead you could use objcopy to stuff the data into some section
> in the executable. Or, just turn the dump to a C file, then compile it
> and do a second link. Aside from (maybe hypothetical) C compiler
> limits, that would be very portable.
Note that having (the option to keep) the dump and the main binary separate can
be a feature. For example, Emacs is often installed in a location that's
writable by root only, and if the dump file can be separate then users can just
redump in a directory that they can write to, without having to copy the entire
Emacs binary.
Separate dump files also makes it easier to experiment with multiple dumps.
Clément.
- Re: pdumping "into" the executable, (continued)
- RE: pdumping "into" the executable, Drew Adams, 2018/02/26
- RE: pdumping "into" the executable, dancol, 2018/02/26
- Re: pdumping "into" the executable, John Wiegley, 2018/02/27
- Re: pdumping "into" the executable, Dmitry Gutov, 2018/02/27
- Re: pdumping "into" the executable, Stefan Monnier, 2018/02/27
- Re: pdumping "into" the executable, John Wiegley, 2018/02/27
- Re: pdumping "into" the executable,
Clément Pit-Claudel <=
- Re: pdumping "into" the executable, Daniel Colascione, 2018/02/26