Hernandez Miramontes, Jose Miguel <jose.miguel.hernandez.miramontes@...>
yes, but if the section is not removed debugger would be able to find the debug symbols. Like how it happens with PDB files.toggle quoted messageShow quoted text
We could leave the symbols in the binaries, but it will consume more space. Space in the SPI is usually a constrain
I am just wondering if it is possible to fix this so that the section is there in the final efi.
If I were to try it, where would I start?
Jose Miguel Hernandez Miramontes
+1 (512) 362-1230
From: Ard Biesheuvel <firstname.lastname@example.org>
Sent: Wednesday, March 24, 2021 10:26 AM
To: Laszlo Ersek <email@example.com>
Cc: firstname.lastname@example.org; Hernandez Miramontes, Jose Miguel <email@example.com>; Feng, Bob C <firstname.lastname@example.org>; Saucedo Tejada, Genaro <email@example.com>; Ortiz Garcia, Jorge E <firstname.lastname@example.org>; Ard Biesheuvel (TianoCore) <email@example.com>
Subject: Re: [edk2-discuss] GccBase.lds
On Wed, 24 Mar 2021 at 16:18, Laszlo Ersek <firstname.lastname@example.org> wrote:
The build-id is used by Linux distros when they ship debug symbols with production shared libraries. The build-id permits the loader to look up the correct file, and confirm that the versions match.
In EDK2, the ELF binary is only an intermediate artifact, and so I fail to see why we would need build IDs here. If the ELF binary was built with debug symbols, they will be in the binary itself, not in a side loaded symbol file.