On 11/23/2016 12:31 AM, Chi-Hsuan Yen via arch-general wrote:
> In glibc, printf calls malloc. See
> http://stackoverflow.com/questions/6743034/does-fprintf-use-malloc-under-the-hood
Yes,
That's not the point. There is generally a know exclusion file that covers
the memory used by fprintf, etc.
On Wed, Nov 23, 2016 at 2:26 PM, David C. Rankin
wrote:
> All,
>
> valgrind is reporting an additional allocation and free along with and
> additional 1M of memory used. Below, 11 bytes should be allocated and freed.
> Instead valgrind reports 1035 bytes. (it's worse if you use strdup). For
> e
All,
valgrind is reporting an additional allocation and free along with and
additional 1M of memory used. Below, 11 bytes should be allocated and freed.
Instead valgrind reports 1035 bytes. (it's worse if you use strdup). For
example:
#include
#include
#include
enum { MAXC = 16 };
int mai
3 matches
Mail list logo
