Hi Frank, On Tue, Aug 26, 2025 at 06:46:04PM -0400, Frank Ch. Eigler wrote: > > This can be used for example to check whether an ELF archive file > > contains ELF members that can be stripped by using: > > eu-classify --ar-member --unstripped <ar-file> > > So one could immediately put this into debugedit's find-debuginfo.sh.
Yes, but it needs a release of elfutils first of course. I probably just reuse some of the code in debugedit to add a detection tool. > > RFC: Is the option name --ar-member clear? Do we also want a variant > > (--all-ar-members) that checks whether all members match? Do we want > > this to work recursively? Should it print the member names that match > > instead of the archive file (is that useful?). > > Suggest "--any-ar-member" to clarify the name, and I wouldn't bother > with the other things. Like that name. Would be like the opposite of --all-ar-members, but there the issue is that there might be some special members which aren't really meant to match. So maybe not implement that for now. > (OTOH, if PR33305 or PR33329 could come into being, this perhaps would > not be needed.) Is anybody working on that? I like the ar --map idea, but have some design questions. Just refusing to handle really large ar files seems too simplistic, you still have a performance problem with packages that just have losts of smaller archives. Cheers, Mark
