glibc

All the bugs discovered by musl, and how many are glibc-related: That's just a crazy number of bugs.

Yes backtrace() and friends is a glibc thing, but libexecinfo tries to be compatible and portable.

Turned-out that it worked basically because of nuances of glibc but was totally not fork safe.

Actually, glibc's argp library (a more featureful alternative to getopt) uses '\v' for a few things (though, not at all for what it is normally used to mean:P).

IME you can statically link glibc, but your statically linked binary will still call ld.so.

Its also useful for creating statically linked executables, which is usually not possible with glibc if you use certain functions (getaddrinfo?).

Commit a race condition to glibc,musl,uclibc and fuck up almost every software on the planet.

It means everything in the world if you've run into a glibc bug, I get that, but it's amazing how few people have done that.

Some of our newer services need a up to date version of glibc and a lot of other dependencies CentOS can't provide.

For the uninitiated, these are libc libraries for embedded systems (alternatives to glibc).

And also the toxic maintainership of glibc in the Drepper era.

I welcome the competition to glibc and think they have some good goals.