Re: [Valgrind-users] Usage and output with memory pools

[Marshall L. <mwl...@gm...>]

Correct me if I've misread the code. It appears that for an address to
be in a recently re-allocated block, it must be contained in a freed
block as well as in an allocated block. How do I get Valgrind to tell me
about the freed block, like it does with malloc/free?

Marshall

On Thu, May 26, 2016 at 03:06:39AM -0700, John Reiser wrote:
> >  ...  The error message only indicates that the address is in one
> > of the memory pools. Valgrind states that the block is "recently
> > re-allocated", a term which I don't understand and which doesn't seem to
> > appear in any of the documentation.
> 
> > ==4888==  Address 0x5c31230 is 4,368 bytes inside a recently re-allocated block of size 65,536 alloc'd
> 
> One advantage of open source is that users can inspect the source code.
> =====
> $ grep -sr 'recently re-allocated' .
> 	...
> ./memcheck/mc_errors.c:      We however detect and report that this is a recently re-allocated
> ./memcheck/mc_errors.c:            ai->Addr.Block.block_desc = "recently re-allocated block";
> 	...
> =====
> Then edit memcheck/mc_errors.c to read the comments and the code.
> Doing so helped me understand the message.
> 
> 
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users