|
From: Petar J. <pe...@so...> - 2019-06-14 10:38:58
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=3c9d1fc4cc8e8fb713b48e0e10e7acffae787ed7 commit 3c9d1fc4cc8e8fb713b48e0e10e7acffae787ed7 Author: Petar Jovanovic <mip...@gm...> Date: Fri Jun 14 10:09:19 2019 +0000 Fix memcheck/tests/leak_cpp_interior failure on 32-bit platforms Update expected file for 32-bit platforms. This is a follow up to: commit bc758374a25e5cfb1a7c11f3ac3b0e31217746a5 Author: Philippe Waroquiers <phi...@sk...> Date: Sat May 18 12:10:40 2019 +0200 Add a test for the new gdbserver adddress[length] syntax. Diff: --- memcheck/tests/leak_cpp_interior.stderr.exp | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/memcheck/tests/leak_cpp_interior.stderr.exp b/memcheck/tests/leak_cpp_interior.stderr.exp index 943b1cc..ae3ae23 100644 --- a/memcheck/tests/leak_cpp_interior.stderr.exp +++ b/memcheck/tests/leak_cpp_interior.stderr.exp @@ -2,8 +2,8 @@ valgrind output will go to log VALGRIND_DO_LEAK_CHECK x bytes in 1 blocks are definitely lost in loss record ... of ... - by 0x........: doit() (leak_cpp_interior.cpp:116) - by 0x........: main (leak_cpp_interior.cpp:131) + by 0x........: doit() (leak_cpp_interior.cpp:119) + by 0x........: main (leak_cpp_interior.cpp:134) LEAK SUMMARY: definitely lost: x bytes in 1 blocks @@ -107,6 +107,10 @@ Searching for pointers pointing in x bytes from 0x........ *0x........ interior points at x bytes inside 0x........ Address 0x........ is 0 bytes inside data symbol "ptr" block at 0x........ considered reachable by ptr 0x........ using newarray heuristic +Searching for pointers pointing in x bytes from 0x........ +*0x........ interior points at x bytes inside 0x........ + Address 0x........ is 0 bytes inside data symbol "ptr" +block at 0x........ considered reachable by ptr 0x........ using newarray heuristic destruct MyClass destruct MyClass destruct MyClass |