@@ -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 )
@@ -502,16 +502,16 @@ $ gdb /opt/node-debug/node core.node.8.1535359906
502
502
$ backtrace
503
503
```
504
504
505
- #### Building an ASAN build
505
+ #### Building an ASan build
506
506
507
- [ ASAN ] ( https://github.com/google/sanitizers ) can help detect various memory
508
- related bugs. ASAN builds are currently only supported on linux.
507
+ [ ASan ] ( https://github.com/google/sanitizers ) can help detect various memory
508
+ related bugs. ASan builds are currently only supported on linux.
509
509
If you want to check it on Windows or macOS or you want a consistent toolchain
510
510
on Linux, you can try [ Docker] ( https://www.docker.com/products/docker-desktop )
511
511
(using an image like ` gengjiawen/node-build:2020-02-14 ` ).
512
512
513
513
The ` --debug ` is not necessary and will slow down build and testing, but it can
514
- show clear stacktrace if ASAN hits an issue.
514
+ show clear stacktrace if ASan hits an issue.
515
515
516
516
``` console
517
517
$ ./configure --debug --enable-asan && make -j4
0 commit comments