https://bugs.kde.org/show_bug.cgi?id=162229
Tom Hughes <t...@compton.nu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |t...@compton.nu
--- Comment #6 from Tom Hughes <t...@compton.nu> ---
No I don't think it's anything to do with word boundaries, rather I suspect
it's actually everything working as expected.
What "possibly lost" means is that valgrind didn't find a pointer to the start
of the allocated block but did find a pointer to an address inside the block.
That is of course exactly what is happening here - inside std::string it is
storing a pointer to the actual string data but that isn't the start of the
block it allocated because it has stashed some metadata before the string data.
I assume it's doing something like storing the length before the start of the
string data?
--
You are receiving this mail because:
You are watching all bug changes.
