https://bugs.kde.org/show_bug.cgi?id=392855
Bug ID: 392855
Summary: valgrind reports 1 additional allocation and 1024
additional bytes allocated (again...)
Product: valgrind
Version: 3.13.0
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Devs,
This is an issue that appears to be a regression of a bug reported to Arch in
June 2016 and has stayed fixed, but now it back again. The arch bug is:
https://bugs.archlinux.org/task/49681
Basically valgrind started reporting an additional allocation and an additional
1024 bytes of memory allocated (for just about every allocation). Within the
last couple of days (I suspect related to changes in gcc-glibc) it now reports
the correct number of allocations, but still reports at least 1024 additional
bytes, e.g.
#include <stdio.h>
#include <stdlib.h>
int main (void) {
int *a = malloc (sizeof *a);
*a = 5;
printf ("a: %d\n", *a);
free (a);
}
valgrind reports:
valgrind ./bin/vgtest2
==15274== Memcheck, a memory error detector
==15274== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==15274== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==15274== Command: ./bin/vgtest2
==15274==
a: 5
==15274==
==15274== HEAP SUMMARY:
==15274== in use at exit: 0 bytes in 0 blocks
==15274== total heap usage: 1 allocs, 1 frees, 1,024 bytes allocated
==15274==
==15274== All heap blocks were freed -- no leaks are possible
==15274==
==15274== For counts of detected and suppressed errors, rerun with: -v
==15274== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
So instead of correctly reporting 4-bytes, valgrind now reports 1024 bytes.
There appears to be a regression not properly handled by the exclusions.
--
You are receiving this mail because:
You are watching all bug changes.
