linux/poky.git/meta/recipes-devtools/valgrind, branch master-test

valgrind: exclude bar_bad/bar_bad_xml from ptests

2020-12-18T22:52:24+00:00

The tests' output is non-deterministic and sometimes doesn't match the sample output. This has been reported at https://bugs.kde.org/show_bug.cgi?id=430321 (see also an earlier related bug https://bugs.kde.org/show_bug.cgi?id=358213) Until upstream figures out how to fix this, let's not run the tests. (From OE-Core rev: 7f7d2fa18267090891754d976cbc3e628324d3dd) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

valgrind: helgrind: Intercept libc functions

2020-11-24T10:27:45+00:00

PTH_FUNC definition needs to be modified in order to intercept posix thread functions in both libc and libpthread. In order to handle this in helgrind, weak alias the pthread functions in glibc. Include a special case for musl. See https://bugs.kde.org/show_bug.cgi?id=428909 for additional discussion. Upstream-Status: Submitted (From OE-Core rev: 5da46a552d54de34a5243e1d90dcc6f52b7af746) Signed-off-by: Paul Floyd Signed-off-by: Stacy Gaikovaia Signed-off-by: Richard Purdie

valgrind: Fix build on musl after drd fixes

2020-10-26T22:08:36+00:00

(From OE-Core rev: 6a74caa115298e594ae22a9de91b132db62e4b5d) Signed-off-by: Richard Purdie

valgrind: drd: fix pthread intercept test failures

2020-10-26T22:08:36+00:00

After glibc uprev 2.31 -> 2.32, the following drd ptests fail with the error "condition variable has not been initialized". drd/tests/annotate_hb_err drd/tests/annotate_sem drd/tests/annotate_rwlock drd/tests/annotate_order_2 drd/tests/annotate_smart_pointer drd/tests/annotate_spinlock drd/tests/monitor_example drd/tests/pth_cond_race drd/tests/pth_inconsistent_cond_wait In glibc 2.32, the POSIX thread functions are in both libc and libpthread, causing valgrind to misinterpert test behaviour. This patch tells valgrind to intercept both the libc and the libpthread functions, resolving these ptest failures. Here are the latest test results on qemux86-64: === Test Summary === TOTAL: 728 PASSED: 688 FAILED: 1 SKIPPED: 39 The failed test is in helgrind: FAIL: helgrind/tests/pth_destroy_cond Patch can be removed once we uprev valgrind. See valgrind commit 15330adf7c2471fbaa6a0818db07078d81dbff97. (From OE-Core rev: e8f265e957e187b4f84f566aaeec8f514e3044d6) Signed-off-by: Stacy Gaikovaia Signed-off-by: Richard Purdie

valgrind: fix memcheck vgtests remove fullpath-after flags

2020-09-17T08:47:46+00:00

Previously in: f75792b28e valgrind: make a few more ptests pass the vagrind test runner was adjusted to suppress part of a path that only exists when run in the yocto ptest environment. Unfortunately this change includes the valgrind version and when valgrind was last updated, the patch was not changed. Rather than continually updating the patch or even generating the version dynamically, we can simply change the expected output for two tests. The reason the option: --fullpath-after=foo was introduced into the effected valgrind ptests was to deal with builds where ccache is used. Compiling with ccache enabled sometimes causes the source file absolute name to be found in a full path that is not the same as $PWD. See commit c80f32e662dfa2a4f046960a25d5b8b7a8821bea in valgrind for more information about changes to the arguments that test badfree3 and varinfo5 run with. There is also a minor fix to add the missing overloading.pm perl package and put the dependencies in alphabetic order. (From OE-Core rev: 9c82b9302c6ee84864e9a9cc870729395804e794) Signed-off-by: Stacy Gaikovaia Signed-off-by: Richard Purdie

valgrind: upgrade 3.16.0 -> 3.16.1

2020-06-25T09:23:37+00:00

??Signed-off-by: Wang Mingyu (From OE-Core rev: faaebe0df4f8e0b742a6c1a32ea5579210559ab9) Signed-off-by: Richard Purdie

valgrind: disable it for powerpc soft-float

2020-06-23T11:31:03+00:00

valgrind doesn't build for powerpc soft-float. It is thus disabled for such architectures. (From OE-Core rev: effd1434a6ca6afcc358bea64053a7bf805633c7) Signed-off-by: Valentin Longchamp Signed-off-by: Richard Purdie

valgrind: upgrade 3.15.0 -> 3.16.0

2020-06-04T12:27:32+00:00

0001-gcc10-arm64-build-needs-__getauxval-for-linking-with.patch 0001-tests-Make-pthread_detatch-call-portable-across-plat.patch 0004-pth_atfork1.c-Define-error-API-for-musl.patch removed since they are included in 3.16.0 refresh 0004-Fix-out-of-tree-builds.patch -License-Update: before: You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA. after: You should have received a copy of the GNU General Public License along with this program; if not, see . (From OE-Core rev: a627a350cf3db99a63d6be2701957e3de0654370) Signed-off-by: Wang Mingyu Signed-off-by: Richard Purdie

valgrind: Backport upstream patch to fix __getauxval needs

2020-05-18T05:33:36+00:00

Drop disabling outline-atomics since that was added to fix this issue in particular (From OE-Core rev: 702a1ae29c6a0f920bd67b7a7a41b886ac52a751) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

valgrind: Do not use outline-atomics on aarch64

2020-05-15T15:31:45+00:00

This avoids the __getauxval undefined reference error seen with gcc10 on doing static linking with -nodefaultlibs, which is uncommon usecase anyway, disabling outline-atomics is not a huge deal for OE in terms of performance as we already use -mcpu which is tuned enough to the SOC the code is being generated for (From OE-Core rev: 3952738d083b888e5b898ed3d63a0ed9a4dd3712) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie