Apparently what BIND was doing was passing a null pointer to qsort and assuming it was ok because nel was 0: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61236 …
-
-
-
#glibc should probably either refrain from putting the nonnull attribute on qsort proto or make it explicitly crash/trap on null pointers. -
@RichFelker FWIW, all runtime violations of the nonnull attribute are caught by -fsanitize=null (part of -fsanitize=undefined).
End of conversation
New conversation -
-
-
@RichFelker several years ago I ran the checker that would be UBSan on BIND and reported a bunch of bugs and never heard anything back -
@RichFelker I guess they enjoy doing things the hard way
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.