author | Nathan Froyd <froydnj@mozilla.com> |
Thu, 23 Jan 2014 16:49:56 -0500 | |
changeset 165640 | 118d5c5d71bbbdce5102c0d570c0f9ac637324cc |
parent 165639 | 23a89fe652c123519497549e4762bde9b8985233 |
child 165641 | ebaa4b58e71cad16d6100f6ad3df7bf59bcfa808 |
push id | 39007 |
push user | nfroyd@mozilla.com |
push date | Tue, 28 Jan 2014 23:35:57 +0000 |
treeherder | mozilla-inbound@118d5c5d71bb [default view] [failures only] |
perfherder | [talos] [build metrics] [platform microbench] (compared to previous push) |
reviewers | njn |
bugs | 963280 |
milestone | 29.0a1 |
first release with | nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
|
last release without | nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
|
--- a/build/automationutils.py +++ b/build/automationutils.py @@ -67,20 +67,27 @@ DEBUGGER_INFO = { "lldb": { "interactive": True, "args": "--", "requiresEscapedArgs": True }, # valgrind doesn't explain much about leaks unless you set the - # '--leak-check=full' flag. + # '--leak-check=full' flag. But there are a lot of objects that are + # semi-deliberately leaked, so we set '--show-possibly-lost=no' to avoid + # uninteresting output from those objects. We set '--smc-check==all-non-file' + # and '--vex-iropt-register-updates=allregs-at-mem-access' so that valgrind + # deals properly with JIT'd JavaScript code. "valgrind": { "interactive": False, - "args": "--leak-check=full" + "args": " ".join(["--leak-check=full", + "--show-possibly-lost=no", + "--smc-check=all-non-file," + "--vex-iropt-register-updates=allregs-at-mem-access"]) } } class ZipFileReader(object): """ Class to read zip files in Python 2.5 and later. Limited to only what we actually use. """