https://bugs.kde.org/show_bug.cgi?id=386945
--- Comment #36 from cur...@gmx.com ---
Seems only partially fixed? On power8, ppc64le, gcc 8.2, and current valgrind
git, the following still fails:
#include <stdlib.h>
#include <string.h>
int main() {
char *foo = calloc(3, 1);
return strcmp(foo, "a");
}
==32113== Memcheck, a memory error detector
==32113== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==32113== Using Valgrind-3.15.0.GIT and LibVEX; rerun with -h for copyright
info
==32113== Command: ../valgrind-strcmp
==32113==
==32113== Invalid read of size 4
==32113== at 0x1806F8: main (valgrind-strcmp.c:8)
==32113== Address 0x4b30044 is 1 bytes after a block of size 3 alloc'd
==32113== at 0x48973E8: calloc (vg_replace_malloc.c:752)
==32113== by 0x1806DF: main (valgrind-strcmp.c:6)
==32113==
==32113== Conditional jump or move depends on uninitialised value(s)
==32113== at 0x180700: main (valgrind-strcmp.c:8)
==32113==
==32113==
==32113== HEAP SUMMARY:
==32113== in use at exit: 3 bytes in 1 blocks
==32113== total heap usage: 1 allocs, 0 frees, 3 bytes allocated
==32113==
==32113== LEAK SUMMARY:
==32113== definitely lost: 3 bytes in 1 blocks
==32113== indirectly lost: 0 bytes in 0 blocks
==32113== possibly lost: 0 bytes in 0 blocks
==32113== still reachable: 0 bytes in 0 blocks
==32113== suppressed: 0 bytes in 0 blocks
==32113== Rerun with --leak-check=full to see details of leaked memory
==32113==
==32113== For counts of detected and suppressed errors, rerun with: -v
==32113== Use --track-origins=yes to see where uninitialised values come from
==32113== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
--
You are receiving this mail because:
You are watching all bug changes.
