From ddbe7422aab1a072c17ad3d24122866b9544a13f Mon Sep 17 00:00:00 2001 From: "bruening@google.com" Date: Mon, 24 Feb 2014 17:00:44 +0000 Subject: Re-enable Dr. Memory's -callstack_use_top_fp_selectively option for Chrome, given recent fixes in callstack walking. BUG=https://code.google.com/p/drmemory/issues/detail?id=851 TBR=zhaoqin@chromium.org Review URL: https://codereview.chromium.org/178143002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252932 0039d316-1c4b-4281-b951-d872f2087c98 --- tools/valgrind/valgrind_test.py | 3 --- 1 file changed, 3 deletions(-) diff --git a/tools/valgrind/valgrind_test.py b/tools/valgrind/valgrind_test.py index be96b9d..59f3347 100644 --- a/tools/valgrind/valgrind_test.py +++ b/tools/valgrind/valgrind_test.py @@ -955,9 +955,6 @@ class DrMemory(BaseTool): proc += self._tool_flags - # DrM i#850/851: The new -callstack_use_top_fp_selectively has bugs. - proc += ["-no_callstack_use_top_fp_selectively"] - # Dr.Memory requires -- to separate tool flags from the executable name. proc += ["--"] -- cgit v1.1