tree a224d099c5ce9ac8d55c09d03fc9992c9d6bf551
parent 72718649e68c7eaf3d0b8cd3deebde198b2ea84d
author njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> 1059068399 +0000
committer njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> 1059068399 +0000


Changed the behaviour of realloc() in Memcheck, Addrcheck and Helgrind.

Previously, when realloc() was asked to make a block bigger, the ExeContext
describing where that block was allocated was increased;  however, if the block
became smaller or stayed the same size, the original ExeContext remained.  This
is correct in one way (that's where the memory manager actually parcelled out
the block) but it's not very intuitive.  This commit changes things so the
ExeContext of a block is always changed upon realloc().  I added a regression
test for it too.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1783 a5019735-40e9-0310-863c-91ae7b9d1cf9