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 <philippe.waroquiers@skynet.be>
Date:   Sat May 18 12:10:40 2019 +0200

    Add a test for the new gdbserver adddress[length] syntax.
This commit is contained in:
Petar Jovanovic 2019-06-14 10:09:19 +00:00
parent 91d53d1167
commit 3c9d1fc4cc

View File

@ -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
@ -103,6 +103,10 @@ LEAK SUMMARY:
multipleinheritance: 0 (-x) bytes in 0 (-2) blocks
To see details of leaked memory, give 'full' arg to leak_check
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"