Clean up a few -faddress-sanitizer stragglers.

chrome/test/pyautolib/asan_stub.c

Index: chrome/test/pyautolib/asan_stub.c
diff --git a/chrome/test/pyautolib/asan_stub.c b/chrome/test/pyautolib/asan_stub.c
index 4fa4686fa282a8214c00ed98f5ee15a0481b8bd5..0826ef0625fb4647422474e533d38fa33a0717e4 100644
--- a/chrome/test/pyautolib/asan_stub.c
+++ b/chrome/test/pyautolib/asan_stub.c
@@ -21,10 +21,10 @@
 //
 // Option (2) is not easy because pyautolib uses code from Chrome
 // (see chrome_tests.gypi, dependencies for target_name: pyautolib) that
-// has been instrumented with ASAN. So even if we disable -faddress-sanitizer
+// has been instrumented with ASAN. So even if we disable -sanitize=address
 // for pyautolib own sources, ASAN instrumentation will creep in from there.
 // To avoid ASAN instrumentation, we might force Chrome build to compile all our
-// dependencies one more time without -faddress-sanitizer.
+// dependencies one more time without -fsanitize=address.
 //
 // Note also that using these empty stubs prevents ASAN from catching bugs in
 // Python-pyautolib process. But we do not need it, we are interested in Chrome