Mailing List Archive

blowup: new debug symbols for PE-64 in EFI blob, xen-4.16 , fc36

everyone has seen how the EFI blob blows up in fc36, so Andrew Cooper
has found a whole new set of symbols in the blob, that can be removed
with `strip -s`

Here is our irc chat:

<ChmEarl> 33431286 Mar 21 05:51 /usr/lib64/efi/xen-4.16.0.efi
<ChmEarl> ^ EFI blob in fc36 is so large, used to be 2.7 MB
<ChmEarl> looking at the xen.spec I can't see why
<andyhhp> debug symbols?
<andyhhp> there's been quite a bit of -pep work going on in binutils
upstream recently
<andyhhp> and I could entirely we've been depending on side effects of
incomplete implementations
<ChmEarl> objdump *xen-4.16.0.efi -> 27672 Apr 7 08:04 hyp-note
<ChmEarl> the .note.package is < 1MB
<ChmEarl> oh, didn't check for the debug flag
<ChmEarl> in xen.hypervisor.config, # CONFIG_DEBUG is not set
<andyhhp> I meant general debug symbols. does `strip -s` make it
substantially smaller
<andyhhp> if not, best reporting it on xen-devel@ identifying which
version of binutils you've got
<ChmEarl> yes, 6MB now, 6386978 Apr 7 08:14 xen-4.16.0.efi
<ChmEarl> 33MB -> 6MB
<ChmEarl> the strip command changed it in-place
<andyhhp> ok - bug report on xen-devel please
<andyhhp> we want to rename that to xen-syms.efi, and strip the thing
which gets eventually called xen-4.16.0.efi
<andyhhp> exactly like we do on the ELF side too
<andyhhp> but yeah - that will be a side effect of newer binutils
knowing how to generate PE64-compatbile debug info