https://bugs.kde.org/show_bug.cgi?id=392855
Philippe Waroquiers <philippe.waroqui...@skynet.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philippe.waroquiers@skynet.
| |be
--- Comment #6 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
Run with
--xtree-memory=full
This will produce a file xtmemory.kcg.<PID>
containing a.o. the information about all stack traces that
have lead to an allocation.
You should then be able to explain the report:
2 allocs, 2 frees, 1,028 bytes allocated
As said by Tom, the second blocks is very likely allocated by some runtime.
And then valgrind properly shows that.
Philippe
--
You are receiving this mail because:
You are watching all bug changes.
