gcc -c provoke_glibc_private_undef.c gcc -o test provoke_glibc_private_undef.o
// fake_res_init.c void __res_maybe_init(void) /* do nothing */ undefined symbol --res-maybe-init version glibc-private
If you (or your package manager) installed a custom-built glibc (e.g., from source with --enable-debug or a vendor-specific patch set), it might export additional private symbols. When you later run a binary linked against that custom glibc on a standard glibc, the symbol is missing. gcc -c provoke_glibc_private_undef
If you see a library listed here, this is your primary suspect. It is likely an antivirus agent (like Carbon Black, CrowdStrike, or Cylance), a performance library, or a custom wrapper. a performance library