unit-test: Set to none after sanitizer
The unit test contains a step to do sanitize test by
`-Db_sanitize=address,undefined`, and remove the config after it's done.
However, the meson generated `compile_commands.json` still contains the
`-fsanitize=address,undefined` compile option. If we run the unit test
again, it will cause valgrind test reporting error as below:
```
ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD.
```
To correctly disable sanitizer, `-Db_sanitize=none` is needed to
specifically tell meson to disable it.
Tested: Run sdbusplus's unit test twice without issue. Without this
change, the second run will get the above valgrind error.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: Iebde8ce80b498a039de4f2713b5c16561ca63b09
diff --git a/scripts/unit-test.py b/scripts/unit-test.py
index 9d79b79..c8c8687 100755
--- a/scripts/unit-test.py
+++ b/scripts/unit-test.py
@@ -1107,7 +1107,12 @@
# '-Db_sanitize=memory')
# check_call_cmd('meson', 'test', '-C', 'build'
# '--logbase', 'testlog-msan')
- meson_flags.remove("-Db_sanitize=address,undefined")
+ meson_flags = [
+ s.replace(
+ "-Db_sanitize=address,undefined", "-Db_sanitize=none"
+ )
+ for s in meson_flags
+ ]
try:
check_call_cmd(
"meson", "setup", "--reconfigure", "build", *meson_flags