HomeSort by relevance Sort by last modified time
    Searched refs:valgrindoutput (Results 1 - 9 of 9) sorted by null

  /external/valgrind/main/memcheck/tests/
long_namespace_xml.stderr.exp 3 <valgrindoutput>
98 </valgrindoutput>
xml1.stderr.exp 3 <valgrindoutput>
434 </valgrindoutput>
  /external/valgrind/main/drd/tests/
fp_race_xml.stderr.exp 3 <valgrindoutput>
103 </valgrindoutput>
annotate_barrier_xml.stderr.exp 3 <valgrindoutput>
331 </valgrindoutput>
bar_bad_xml.stderr.exp 3 <valgrindoutput>
314 </valgrindoutput>
thread_name_xml.stderr.exp 3 <valgrindoutput>
442 </valgrindoutput>
  /external/valgrind/main/exp-sgcheck/tests/
hsg.stderr.exp 3 <valgrindoutput>
115 </valgrindoutput>
  /external/valgrind/main/helgrind/tests/
tc06_two_races_xml.stderr.exp 3 <valgrindoutput>
266 </valgrindoutput>
  /external/chromium_org/tools/valgrind/
memcheck_analyze.py 369 f.write("</valgrindoutput>\n")
372 if '</valgrindoutput>' in line:
373 # Valgrind often has garbage after </valgrindoutput> upon crash.
507 " bytes of junk were after </valgrindoutput> in %s!" %

Completed in 653 milliseconds