Handling failure when _rtld_global set as private

[dubeyabhishek]

@giulianobelinassi In latest glibc versions, _rtld_global is marked private in distro packages. On one side its good w.r.t. security perspective, whereas its not good for libpulp. I am curious in knowing, how SLES handles this issue on latest glibc versions? I don't see a way to resolve this issue dynamically, since most of ld*so binaries are stripped on distros.

[giulianobelinassi]

Hello! Sorry for not answering this before, I just found the email notification about this message today!

It is still being handled the same way we do even back to glibc 2.31 in 15.4. Libpulp has a custom symbol loader that iterates on PHDR to actually find the symbol string and compute the address for it, and I know this little symbol loader have some behavior that differs from dlsym in ways I don't understand. The symbol in question (_rtld_global) is still being exported even if it is declared as private, and this symbol loader is able to find it.

I hope I answered your question!