[valgrind] [Bug 372909] glibc 2.23+ fopen/printf change causes valgrind to report 1024 byte allocation

https://bugs.kde.org/show_bug.cgi?id=372909 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com

[valgrind] [Bug 372909] glibc 2.23+ fopen/printf change causes valgrind to report 1024 byte allocation

https://bugs.kde.org/show_bug.cgi?id=372909 David Rankin changed: What|Removed |Added Resolution|INVALID |---

[valgrind] [Bug 372909] glibc 2.23+ fopen/printf change causes valgrind to report 1024 byte allocation

https://bugs.kde.org/show_bug.cgi?id=372909 --- Comment #2 from David Rankin --- Really?? You don't see the difference?? total heap usage: 0 allocs, 0 frees, 0 bytes allocated -- CORRECT total heap usage: 1 allocs, 1 frees, 1,024 bytes allocated -- FUBAR Same

[valgrind] [Bug 372909] glibc 2.23+ fopen/printf change causes valgrind to report 1024 byte allocation

https://bugs.kde.org/show_bug.cgi?id=372909 Tom Hughes changed: What|Removed |Added Resolution|--- |INVALID