The actual story: BIND had a nasty bug and ISC failed to mention that it was UB in their code, blamed gcc. Typical.https://twitter.com/hashbreaker/status/668787790738538497 …
-
-
#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 -
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.