On 11/24/2016 09:02 AM, Chi-Hsuan Yen via arch-general wrote: > OK I found the cause of the extra malloc() call. Since glibc 2.23 > printf uses malloc instead of mmap to allocate file buffers. If you > want to keep the old behavior, keep the old glibc. > > See https://sourceware.org/bugzilla/show_bug.cgi?id=16734 > > Best, > > Yen, Chi-Hsuan Ah Hah! Thank you! That's makes sense, so it is the glibc 2.23 change from mmap to malloc that does it. I suspect that valgrind will be fixed to exclude the printf allocation shortly. Keeping 2.22 isn't worth it just for the old valgrind behavior. I'll check with the valgrind folks and see if that is in the works. -- David C. Rankin, J.D.,P.E.
