Compressed exec and core files
Paul Koning
paul_koning@dell.com
Fri Jan 23 21:47:00 GMT 2015
> On Jan 23, 2015, at 3:37 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Fri, Jan 23, 2015 at 12:30 PM, Michael Eager <eager@eagerm.com> wrote:
>> On 01/23/15 12:19, H.J. Lu wrote:
>>>
>>> On Fri, Jan 23, 2015 at 12:02 PM, Michael Eager <eager@eagerm.com> wrote:
>>> ...
>>> Are you going to fork/exec gzip/bzip2 for this or call zlib/bzip2-libs?
>>
>>
>> Could do either. Exec is simpler. libz.so is currently a dependency,
>> adding libbzip2.so wouldn't be a big deal, but this might be a slippery
>> slope, where each added compression results in another library dependency.
>>
>> Using exec means that the decompress program needs to be on the path, but
>> the failure mode if it is not found is pretty transparent.
>>
>
> I really don't like fork/exec. I strongly prefer zlib/bzip2-libs. You can
> use dlopen to load compression library on demand.
Agreed, fork/exec is a hack that should be used only if no other option exists. Libraries are far better.
paul
More information about the Binutils
mailing list