| 870f170ccce872764e974b86f55247c0d97dc634 |
|
16-Feb-2009 |
njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> |
Stack traces for Memcheck's syscall param errors are terribly unreliable, so
I changed it to just filter the entire stack trace out for these errors (both
normal and XML cases). The syscall name is still present in the error
string. This allows a one or more alternative expected output files to be
removed for several tests, which is A Very Good Thing.
Also, I killed filter_test_paths because it was weird and clumsy and the
above change obviated most of its use and the remaining effects could be
achieved in other ways.
Also, I fixed up the scalar* tests a little and they now pass on my machine,
(and hopefully at least some other machines) for the first time ever!
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@9178 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/malloc_free_fill.stderr.exp
|
| 131defc8fe453160005c4e619a6d79b594c35e1b |
|
08-Nov-2008 |
sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> |
Update expected output now that Memcheck's realloc implementation always
moves the block, even when the new block is smaller or the same size.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8742 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/malloc_free_fill.stderr.exp
|
| edbf716cc183b669fc5dbcc8cc5ed7e4e02c14c4 |
|
27-Jun-2008 |
bart <bart@a5019735-40e9-0310-863c-91ae7b9d1cf9> |
Added extra filtering for the stderr output of malloc_free_fill such that the output of this test becomes independent of the Linux distribution the test is run on. Should fix #162819.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8285 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/malloc_free_fill.stderr.exp
|
| effcfabdf754bf9d3dafc74cff812a788e64ae32 |
|
05-Dec-2007 |
sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> |
Update expected outputs. Use new naming scheme now permitted by
tests/vg_regtest.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7277 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/malloc_free_fill.stderr.exp
|
| eb0fa9345010077e1e4852b238dde303b8f271b3 |
|
30-Nov-2007 |
sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> |
New options for Memcheck, --malloc-fill=<hexnumber> and
--fill-free=<hexnumber>, which cause malloc'd(etc) and free'd(etc)
blocks to be filled with the specified value. This can apparently be
useful for shaking out hard-to-track-down memory corruption. The
definedness/addressability of said areas is not affected -- only the
contents. Documentation to follow.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7259 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/malloc_free_fill.stderr.exp
|