On 05.01.2018 22:24, maya%netbsd.org@localhost wrote: >> Register new weak symbol in libc for internal usage: atoi > > Why are we protecting libc from users who override standard C functions? > I don't think you should be able to provide a wrong implementation of > them, link to libc, and expect it to work. > I'm incercepting atoi(3) & other functions in sanitizers. I cannot reliably intercept them within libc internals (e.g. I'm marking certain data under pointer as initialized, but not inside libc), this change allows to keep libc as a black-box for those who overwrite atoi() in 3rd party software and expect libc to still work as is.
Description: OpenPGP digital signature