tools/valgrind/asan/asan_symbolize.py does not seem to be applied to stack traces produced by (some) asan bots anymore.

A concrete example: https://ci.chromium.org/buildbot/tryserver.chromium.linux/linux_chromium_asan_rel_ng/530118 showed the following failure for PasswordManagerBrowserTestBase.InternalsPage_Renderer:

BrowserTestBase received signal: Terminated. Backtrace:
#0 0x000007c64f71 (/b/s/w/ir/out/Release/browser_tests+0x7c64f70)
#1 0x0000134b3a4c (/b/s/w/ir/out/Release/browser_tests+0x134b3a4b)
#2 0x000014bbe0b6 (/b/s/w/ir/out/Release/browser_tests+0x14bbe0b5)
#3 0x7f1ca5787cb0 (/lib/x86_64-linux-gnu/libc-2.19.so+0x36caf)
...

More context on https://groups.google.com/a/chromium.org/forum/?fromgroups#!topic/chromium-dev/svZ7A-II0a8