]> git.ipfire.org Git - thirdparty/valgrind.git/commit
Use global vars to point at possibly leaked
authorPhilippe Waroquiers <philippe.waroquiers@skynet.be>
Mon, 30 Sep 2013 21:17:09 +0000 (21:17 +0000)
committerPhilippe Waroquiers <philippe.waroquiers@skynet.be>
Mon, 30 Sep 2013 21:17:09 +0000 (21:17 +0000)
commit0925d04c4e58afb15845c8e45fc83905d6767cce
tree03625185e526a50c81ad8fc9aa76dba54964da0f
parent665798c26ed3d044a0c6cefbc8241af6cf3af0fc
Use global vars to point at possibly leaked
Depending on the compiler or optimisation level, the blocks that
are supposed to be possibly leaked are still reachable.
=> change the pointers to be global variables,
and do the allocation in a function, not in main.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13591
memcheck/tests/leak_cpp_interior.cpp
memcheck/tests/leak_cpp_interior.stderr.exp
memcheck/tests/leak_cpp_interior.stderr.exp-64bit