glibc 2.26 mtrace broken, missing allocations

DJ Delorie
Thu Apr 5 21:01:00 GMT 2018

"Carlos O'Donell" <> writes:
> DJ, You've been poking at this area, any thoughts?

The only thing I can think of off-hand is, that it's a malloc that
happened before mtrace() was called.  This can happen if, for example,
there's a ctor/init function that's called before main().

Using ltrace to find any pre-mtrace allocs might be fruitful.

Or my malloc trace branch, which hooks sooner than main().

More information about the Libc-help mailing list