Run memcheck/tests/demangle with -q.

The interesting part is the demangled backtrace in the error message.
Suppress the memory allocation/blocks summary which can differ slightly
depending on the underlying arch/libs.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15308
This commit is contained in:
Mark Wielaard 2015-06-03 09:52:00 +00:00
parent 8e6d249a36
commit 10816c8683
2 changed files with 1 additions and 11 deletions

View File

@ -1,16 +1,5 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: abc::def<int, magic<int> >::xyzzy(int*, magic<int>*) (demangle.cpp:9)
by 0x........: magic<int>::xyzzy(int*) (demangle.cpp:19)
by 0x........: main (demangle.cpp:27)
HEAP SUMMARY:
in use at exit: 6 bytes in 3 blocks
total heap usage: 3 allocs, 0 frees, 6 bytes allocated
For a detailed leak analysis, rerun with: --leak-check=full
For counts of detected and suppressed errors, rerun with: -v
Use --track-origins=yes to see where uninitialised values come from
ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

View File

@ -1 +1,2 @@
prog: demangle
vgopts: -q