[Valgrind-users] 回复： reply： helgrind use more than 32G memory.

[王阳 <412...@qq...>]

HI Philippe,


》memory is to use --stats=yes and post the result here.
>Really, it is really the best way :).
I can not export log from my PC, because PC is isolated from internet.
Can I take a photo of log to you or Can pick up some key information from log to you.
By the way, the size of email is limited to 40KB, am I right? so posting a photo maybe not work out. 


> HI Philippe,
>  I read valgrind user manual, there are some hints which are related
> to my problem I guess. As follows,
> Myprog uses tons of mmap and memory pool ,and do not use free/delete
> to give back memory to pool.
> My question is that If mypog use memoy pool without free/delete and
> don't use VALGRIND_HG_CLEAN_MEMORY will lead to myprog do mmap
> endlessly until use 64G memory?
No, HG_CLEAN_MEMORY is not useful to use less memory.
It is only useful if you recycle memory, and you get
false positive race errors due to this recycling.

The best way to understand where valgrind/helgrind spends
memory is to use --stats=yes and post the result here.
Really, it is really the best way :).
If it takes too long to reach the end (or it crashes
before producing the stats),
you can from the command line use
   vgdb v.info stats
to get the needed info while helgrind is running.

Philippe