Re: [Valgrind-users] Are valgrind leak-check results valid iftarget allocates a block larger than 4G?

[WAROQUIERS P. <phi...@eu...>]

>Bart suggest that I try --freelist-vol=0, but upon doing so I did not
>see any difference (will try again to make sure).
This is normal it makes (almost) no difference as the
freelist-vol default value is small (20 Mb) (and the problem
is rather related to the way Valgrind handles the realloc.
>
>Phillippe suggested I try a patch (
>https://bugs.kde.org/show_bug.cgi?id=250101 ).  I will look into how
>much effort is involved.  I haven't previously built valgrind from
>source.  Sounds like it is in SVN (which I have used for my own
>stuff).  Probably easy to build but I have a couple other ideas to try
>before I will go that route.
The patch solves the problem on your small program (it runs till the
end without (re-)alloc problems and without memleak.
But for sure, a single allocation is much more efficient and less
problematic.

Philippe

____
 
This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful.
 
Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy.
 
Any views expressed in this message are those of the sender.