For golang processes, we collect (golang version, libc, link) as metadata. It'll be useful to collect the "stripped" / "not stripped" status (per reported by file), to help debugging cases where symbols are missing due to stripping.
$ file /bin/ls
/bin/ls: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=897f49cafa98c11d63e619e7e40352f855249c13, for GNU/Linux 3.2.0, stripped
so my ls is stripped.
Do not implement by actually running file, though - use pyelftools like we currently use it, to find the information file looks at, and add a filed stripped: boolean in the metadata.
For golang processes, we collect (golang version, libc, link) as metadata. It'll be useful to collect the "stripped" / "not stripped" status (per reported by file), to help debugging cases where symbols are missing due to stripping.
so my
lsis stripped. Do not implement by actually runningfile, though - usepyelftoolslike we currently use it, to find the informationfilelooks at, and add a filedstripped: booleanin the metadata.