[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:       David Rankin <bugzilla_noreply () kde ! org>
Date:       2018-04-30 20:08:48
Message-ID: bug-392855-17878-n1Tl0vgewj () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #3 from David Rankin <drankinatty@suddenlinkmail.com> ---
Tom,

  I do think you were on to the cause, but this appears to be an issue that
will need to be fixed between valgrind and libc. The assembly generated on
openSuSE Leap 42.3 with gcc 4.8.5 shows a malloc, so I suspect this is where
valgrind tabulates the amount of memory allocated.

  However on the new gcc 7.3, there is no 'call malloc' in the generated
assembly which leaves valgrind to report some default allocation block size.

  Wherever this bug belongs, it need to be fixed. It makes no sense from a
teaching standpoint to have to say: 

"Look at the valgrind output, but only look at the number of allocations and
frees to validate you have freed the memory you allocated. You can't really
look at the amount allocated because valgrind doesn't correctly report the
amount of memory allocated anymore..."

  This tool needs to work correctly from that standpoint as well.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]