@@ -29,7 +29,7 @@ file a new issue.
29
29
* [ Running Coverage] ( #running-coverage )
30
30
* [ Building the documentation] ( #building-the-documentation )
31
31
* [ Building a debug build] ( #building-a-debug-build )
32
- * [ Building an ASAN build] ( #building-an-asan-build )
32
+ * [ Building an ASan build] ( #building-an-asan-build )
33
33
* [ Speeding up frequent rebuilds when developing] ( #speeding-up-frequent-rebuilds-when-developing )
34
34
* [ Troubleshooting Unix and macOS builds] ( #troubleshooting-unix-and-macos-builds )
35
35
* [ Windows] ( #windows )
@@ -507,16 +507,16 @@ $ gdb /opt/node-debug/node core.node.8.1535359906
507
507
$ backtrace
508
508
```
509
509
510
- #### Building an ASAN build
510
+ #### Building an ASan build
511
511
512
- [ ASAN ] ( https://github.com/google/sanitizers ) can help detect various memory
513
- related bugs. ASAN builds are currently only supported on linux.
512
+ [ ASan ] ( https://github.com/google/sanitizers ) can help detect various memory
513
+ related bugs. ASan builds are currently only supported on linux.
514
514
If you want to check it on Windows or macOS or you want a consistent toolchain
515
515
on Linux, you can try [ Docker] ( https://www.docker.com/products/docker-desktop )
516
516
(using an image like ` gengjiawen/node-build:2020-02-14 ` ).
517
517
518
518
The ` --debug ` is not necessary and will slow down build and testing, but it can
519
- show clear stacktrace if ASAN hits an issue.
519
+ show clear stacktrace if ASan hits an issue.
520
520
521
521
``` console
522
522
$ ./configure --debug --enable-asan && make -j4
0 commit comments