Added a stderr filter for new_override, that removes the exact numbers for

malloc, because different glibc versions seem to allocate different amounts of
memory.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1446
This commit is contained in:
Nicholas Nethercote 2003-02-26 10:16:02 +00:00
parent b891391739
commit 18199aae8a
4 changed files with 10 additions and 3 deletions

View File

@ -9,7 +9,7 @@
## strict EIP updating
##---------------------------------------------------------------------------
noinst_SCRIPTS = filter_leak_check_size filter_stderr
noinst_SCRIPTS = filter_allocs filter_leak_check_size filter_stderr
EXTRA_DIST = \
$(noinst_SCRIPTS) \

6
memcheck/tests/filter_allocs Executable file
View File

@ -0,0 +1,6 @@
#! /bin/sh
./filter_stderr | \
sed "s/malloc\/free: in use at exit: [0-9]\+ bytes in [0-9]\+ blocks./malloc\/free: in use at exit: ... bytes in ... blocks./" | \
sed "s/malloc.free: [0-9]\+ allocs, [0-9]\+ frees, [0-9]\+ bytes allocated./malloc\/free: ... allocs, ... frees, ... bytes allocated./"

View File

@ -5,7 +5,7 @@ Conditional jump or move depends on uninitialised value(s)
by 0x........: (within /.../tests/new_override)
ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 0 from 0)
malloc/free: in use at exit: 32 bytes in 1 blocks.
malloc/free: 1 allocs, 0 frees, 32 bytes allocated.
malloc/free: in use at exit: ... bytes in ... blocks.
malloc/free: ... allocs, ... frees, ... bytes allocated.
For a detailed leak analysis, rerun with: --leak-check=yes
For counts of detected errors, rerun with: -v

View File

@ -1 +1,2 @@
prog: new_override
stderr_filter: filter_allocs