summaryrefslogtreecommitdiffstats
path: root/tools/valgrind/memcheck_analyze.py
diff options
context:
space:
mode:
authordank@chromium.org <dank@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-07-28 00:35:48 +0000
committerdank@chromium.org <dank@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-07-28 00:35:48 +0000
commitce2719f53fc08892fb759c722b73a0ac88567982 (patch)
tree5d5bf61fe7066cf8046bce9bf7dc58125d75d77b /tools/valgrind/memcheck_analyze.py
parent5c0767d1facaf222cd17956fdf40618173f46a0e (diff)
downloadchromium_src-ce2719f53fc08892fb759c722b73a0ac88567982.zip
chromium_src-ce2719f53fc08892fb759c722b73a0ac88567982.tar.gz
chromium_src-ce2719f53fc08892fb759c722b73a0ac88567982.tar.bz2
While we're trying to diagnose the incomplete valgrind logfile problem,
output the last 100 lines of the incomplete log(s). We can remove this later. BUG=17453 TEST=modify valgrind to output </XXXvalgrindoutput> at end, verify last 100 lines show up in log Review URL: http://codereview.chromium.org/159437 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@21763 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/valgrind/memcheck_analyze.py')
-rwxr-xr-xtools/valgrind/memcheck_analyze.py3
1 files changed, 3 insertions, 0 deletions
diff --git a/tools/valgrind/memcheck_analyze.py b/tools/valgrind/memcheck_analyze.py
index 3c3b2bb..c8c566a 100755
--- a/tools/valgrind/memcheck_analyze.py
+++ b/tools/valgrind/memcheck_analyze.py
@@ -256,6 +256,9 @@ class MemcheckAnalyze:
continue
if len(badfiles) > 0:
logging.warn("valgrind didn't finish writing %d files?!" % len(badfiles))
+ for file in badfiles:
+ logging.warn("Last 100 lines of %s :" % file)
+ os.system("tail -n 100 '%s'" % file)
def Report(self):
if self._parse_failed: