https://bugs.kde.org/show_bug.cgi?id=392855
Tom Hughes <t...@compton.nu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
CC| |t...@compton.nu
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Tom Hughes <t...@compton.nu> ---
We just report what happens so I doubt this is a valgrind bug, especially if
you say it changed without the version of valgrind changing?
Equally it can't really be a glibc bug, unless the malloc has become a macro
that wraps the real function call, as we intercept the function call.
Most likely the compiler has decided to round up the allocation or something,
but I think the compiled is the most likely place to look. Really given how
small the program is I would just look at the generated assembly to see what is
going on.
--
You are receiving this mail because:
You are watching all bug changes.
