Summary: | glibc 2.23+ fopen/printf change causes valgrind to report 1024 byte allocation | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | David Rankin <drankinatty> |
Component: | general | Assignee: | Julian Seward <jseward> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | mark, tom |
Priority: | NOR | ||
Version: | 3.12 SVN | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
David Rankin
2016-11-25 06:44:04 UTC
What exactly is the problem here? Your program allocates and frees some memory, and valgrind accurately reports that. This is no different to any other library function that you use happening to allocate some memory and is the expected behaviour. 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 code... Whether or not different implementations of that function allocate and free memory is an implementation detail of that library. valgrind accurately reports the memory usage. If you believe the allocation of memory in your program is wrong because of the particular glibc printf implementation report a bug against glibc. |