> Hi, > > On Tue, 2022-12-20 at 22:35 +0100, Mark Wielaard wrote: >> On Wed, Jun 01, 2022 at 10:55:27AM -0500, Guillermo E. Martinez via >> Elfutils-devel wrote: >> > This is the second version patch to avoid remove the CTF section in >> > stripped files. Changes from v1: >> > >> > - Add description in tests/run-strip-remove-keep-ctf.sh >> > mentioning how to regenerate test input file (testfile-ctf) >> > >> > Please let me know your thoughts. >> > >> > [...] >> > >> > CTF debug format was designed to be present in stripped files, so >> > this section should not be removed, so a new --remove-ctf option >> > is added to indicate explicitly that .ctf section will be stripped >> > out from binary file. >> >> Sorry, I see I never reviewed this v2 variant. I know we tried to >> coordinate with binutils so eu-strip and binutils strip would do the >> same thing. And that Jose had an idea for a new section flag to >> automatically detect what section should/shouldn't be stripped (into a >> separate .debug file). What was the conclusion of that? > > Any update on this? > How should .ctf sections be dealt with by strip like tools?
I think the conclusion was that having a NOSTRIP flag in the object file is far from trivial, because what "strip" means for several people and tools is not clear. So I guess we are stuck with the old keep-a-list method. Or we may add NOSTRIP meaning "_never ever_ strip this section, period, no matter what."