Explore >> Select a destination

You are here

 www.productive-cpp.com
Hardening C/C++ Programs Part II - Executable-Space Protection and ASLR - Productive C++
| | jbytecode.github.io
juliac
3.9 parsecs away

Travel
| |
| | stoppels.ch
Executable shared ELF files
2.7 parsecs away

Travel
| |
| | shrik3.com
// DRAFT // ELF, symbol table, and dynamic linking - SHRIK3
3.4 parsecs away

Travel
| |
| | jmmv.dev
Picking glibc versions at runtime - Julio Merino (jmmv.dev)
25.0 parsecs away

Travel
| In a recent work discussion, I came across an argument that didn't sound quite right. The claim was that we needed to set up containers in our developer machines in order to run tests against a modern glibc. The justifications were that using LD_LIBRARY_PATH to load a different glibc didn't work and statically linking glibc wasn't possible either. But... running a program against a version of glibc that's different from the one installed on the system seems like a pretty standard requirement, doesn't it?...