chromium/src
0
Fork 0
Code Activity
Files
c190d34ab24e9a70f2866e33aaa4732bcbf429f5
src/docs/testing/linux_running_asan_tests.md
Lei Lei 8aa9db627d Move testing related docs into testing/ folder and update doc index. 
This CL moves the following md files:
android_test_instructions.md
ipc_fuzzer.md
linux_running_asan_tests.md
test_descriptions.md
web_tests_linux.md

Change-Id: I88dd14f5c98b79a23f5607dbddd1e5b36eb41812
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1578589
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Lei Lei <leilei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#655750}
2019-05-01 21:08:01 +00:00

779 B
Raw Blame History

Running Chrome tests with AddressSanitizer (asan) and LeakSanitizer (lsan)

Running asan/lsan tests requires changing the build and setting a few environment variables.

Changes to args.gn (ie, out/Release/args.gn):

is_asan = true
is_lsan = true

Setting up environment variables and running the test:

$ export ASAN_OPTIONS="symbolize=1 external_symbolizer_path=./third_party/llvm-build/Release+Asserts/bin/llvm-symbolizer detect_leaks=1 detect_odr_violation=0"
$ export LSAN_OPTIONS=""
$ out/Release/browser_tests

Stack traces (such as those emitted by base::debug::StackTrace().Print()) may not be fully symbolized. The following snippet can symbolize them:

$ out/Release/browser_tests 2>&1 | ./tools/valgrind/asan/asan_symbolize.py