diff options
| author |   Benoît Ganne <bganne@cisco.com> | 2020-04-21 19:25:14 +0200 |
|---|---|---|
| committer |   Dave Barach <openvpp@barachs.net> | 2020-04-22 13:04:00 +0000 |
| commit | 332bc084dd15a2c7b7b26bb00775c835c9630e8a (patch) | |
| tree | 6fb6b0d26e41afde56d09d59f368387d72b07600 /docs/troubleshooting | |
| parent | 703128816ff8504340dcb512ff05935dab6b2e40 (diff) | |
misc: asan: disable leak sanitizer by default
Leak Sanitizer is not stable yet with VPP. It can always be enabled at
runtime with ASAN_OPTIONS=detect_leaks=1.
Type: fix
Change-Id: Ieff01091e2976e127783ebd331cd0e50a1dbca12
Signed-off-by: Benoît Ganne <bganne@cisco.com>
Diffstat (limited to 'docs/troubleshooting')
| -rw-r--r-- | docs/troubleshooting/sanitizer.rst | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/docs/troubleshooting/sanitizer.rst b/docs/troubleshooting/sanitizer.rst index d4e9a4da4c5..a63720ffe42 100644 --- a/docs/troubleshooting/sanitizer.rst +++ b/docs/troubleshooting/sanitizer.rst @@ -35,12 +35,10 @@ build option, so all VPP targets should be supported. For example: $ make test-debug TEST=test_gbp VPP_EXTRA_CMAKE_ARGS=-DENABLE_SANITIZE_ADDR=ON .... -Once VPP has been built with ASan support, you can use it as usual. When -running under a debugger it can be useful to disable LeakSanitizer which is -not compatible with a debugger and displays spurious warnings at exit: - +Once VPP has been built with ASan support you can use it as usual including +under gdb: .. code-block:: console - $ ASAN_OPTIONS=detect_leaks=0 gdb --args $PWD/build-root/install-vpp_debug-native/vpp/bin/vpp "unix { interactive }" + $ gdb --args $PWD/build-root/install-vpp_debug-native/vpp/bin/vpp "unix { interactive }" .... |