History log of /external/valgrind/memcheck/tests/writev1.stderr.exp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
7cbe0688bc1ac313110dee71966a5d958f8c7066 25-Apr-2015 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Fix the writev / readv wrappers. Do not read the array pointed to
by the 2nd argument, if the element count is negative.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15143 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/writev1.stderr.exp
8e0cc77568a112a1a2a55be05a09d6b1c900016c 04-Oct-2011 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Turns out there is at least one version of glibc tat contains
a file name writev.c. This screws our filename based backtrace
filtering. Rename writev to writev1 to avoid that problem.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12093 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/writev1.stderr.exp