File: linux_running_asan_tests.md

package info (click to toggle)
chromium 73.0.3683.75-1~deb9u1
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 1,792,156 kB
  • sloc: cpp: 13,473,466; ansic: 1,577,080; python: 898,539; javascript: 655,737; xml: 341,883; asm: 306,070; java: 289,969; perl: 80,911; objc: 67,198; sh: 43,184; cs: 27,853; makefile: 12,092; php: 11,064; yacc: 10,373; tcl: 8,875; ruby: 3,941; lex: 1,800; pascal: 1,473; lisp: 812; awk: 41; jsp: 39; sed: 19; sql: 3
file content (26 lines) | stat: -rw-r--r-- 779 bytes parent folder | download | duplicates (13) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
 
# 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`):

```python
is_asan = true
is_lsan = true
```

Setting up environment variables and running the test:

```sh
$ 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:

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