ligang/vpp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

misc: asan: disable leak sanitizer by default

Browse Source 
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>
This commit is contained in:
Benoît Ganne
2020-04-21 19:25:14 +02:00
committed by Dave Barach
parent 703128816f
commit 332bc084dd
2 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/troubleshooting/sanitizer.rst
View File

@ -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 }"
....

3
src/vpp/vnet/main.c
View File

@ -512,7 +512,8 @@ VLIB_CLI_COMMAND (show_bihash_command, static) =
const char *
__asan_default_options (void)
{
return "unmap_shadow_on_exit=1:disable_coredump=0:abort_on_error=1";
return
"unmap_shadow_on_exit=1:disable_coredump=0:abort_on_error=1:detect_leaks=0";
}
#endif /* CLIB_SANITIZE_ADDR */