@@ -29,7 +29,7 @@ file a new issue.
2929 * [ Running Coverage] ( #running-coverage )
3030 * [ Building the documentation] ( #building-the-documentation )
3131 * [ 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 )
3333 * [ Speeding up frequent rebuilds when developing] ( #speeding-up-frequent-rebuilds-when-developing )
3434 * [ Troubleshooting Unix and macOS builds] ( #troubleshooting-unix-and-macos-builds )
3535 * [ Windows] ( #windows )
@@ -502,16 +502,16 @@ $ gdb /opt/node-debug/node core.node.8.1535359906
502502$ backtrace
503503```
504504
505- #### Building an ASAN build
505+ #### Building an ASan build
506506
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.
509509If you want to check it on Windows or macOS or you want a consistent toolchain
510510on Linux, you can try [ Docker] ( https://www.docker.com/products/docker-desktop )
511511(using an image like ` gengjiawen/node-build:2020-02-14 ` ).
512512
513513The ` --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.
515515
516516``` console
517517$ ./configure --debug --enable-asan && make -j4
0 commit comments