From f286da271cbb58a1bc17726a32aaac6c588aee18 Mon Sep 17 00:00:00 2001 From: Masatake YAMATO Date: Sun, 20 Dec 2020 01:31:43 +0900 Subject: [PATCH] GitHub Actions: don't excuse building ctags executable with -O0 option https://www.valgrind.org/docs/manual/quick-start.html Compile your program with -g to include debugging information so that Memcheck's error messages include exact line numbers. Using -O0 is also a good idea, if you can tolerate the slowdown. With -O1 line numbers in error messages can be inaccurate, although generally speaking running Memcheck on code compiled at -O1 works fairly well, and the speed improvement compared to running -O0 is quite significant. Use of -O2 and above is not recommended as Memcheck occasionally reports uninitialised-value errors which don't really exist. Suggested by @leleliu008 at https://github.com/universal-ctags/ctags/pull/2747 --- .github/workflows/testing-with-vlagrind.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/testing-with-vlagrind.yml b/.github/workflows/testing-with-vlagrind.yml index c06159f543..26c0146926 100644 --- a/.github/workflows/testing-with-vlagrind.yml +++ b/.github/workflows/testing-with-vlagrind.yml @@ -7,7 +7,7 @@ on: branches: [ master ] jobs: - testing-O0_fixme: + testing: runs-on: ubuntu-latest