3 ms·
That message happens when a new binary is run on an old glibc, not the other way around.
by floatboth 7y ago
That message happens when a new binary is run on an old glibc, not the other way around.
- ur-whale 7y agoYes, you'd think so indeed. Unfortunately, I've seen the exact opposite in production: older binary running atop newer glibc and crashing with that kind of message. glibc abi compatibility is and has been a joke.