[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 392855] valgrind reports 1 additional allocation and 1024 additional bytes allocated
From:       Philippe Waroquiers <bugzilla_noreply () kde ! org>
Date:       2018-05-06 21:40:53
Message-ID: bug-392855-17878-cpfZvfl976 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=392855

Philippe Waroquiers <philippe.waroquiers@skynet.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |philippe.waroquiers@skynet.
                   |                            |be

--- Comment #6 from Philippe Waroquiers <philippe.waroquiers@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.=
[prev in list] [next in list] [prev in thread] [next in thread]