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

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

valgrind: Fix timerfd syscall test to be 64bit time_t safe

2020-03-11T11:44:28+00:00

This helps compile the testcase with musl on 32bit arches (From OE-Core rev: ac5a65cb5fdb315df2cb016d0cc5c3389c7971f0) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

valgrind: Fix ptest builds on musl

2020-02-02T16:57:21+00:00

(From OE-Core rev: 20e7d638322cf03f512d4f13c698f25211097f86) Signed-off-by: Khem Raj Cc: Alexander Kanavin Signed-off-by: Richard Purdie

valgrind: fix the remaining ptest failures

2020-02-02T16:57:21+00:00

Particularly, one test is disabled as it is failing everywhere, two patches that actually cause failures are dropped and some binaries are prevented from being stripped where that is expected. (From OE-Core rev: 64bc13f3c9c96584494f0984da5253a306e8a140) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

valgrind: partially fix ptests

2020-01-16T22:33:09+00:00

Unfortunately the ptests assume that $S=$B, and also require the presence of original source code. There are still some failures left which require additional investigation. (From OE-Core rev: f781e2a70ce1086c49e0c3d5ac61b7bf5bd79a9c) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

valgrind: Fix build with -fno-common

2019-12-30T08:47:12+00:00

(From OE-Core rev: 14f14eccf176539493fbfe710b66704feb7710da) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

valgrind: disable 256 ptests for aarch64

2019-09-16T22:02:44+00:00

On qemuarm64 systems, about half of the valgrind tests fail and often result in defunct processes, eg: root 819 818 25 00:12 pts/0 00:01:52 /usr/bin/valgrind --command-line-only=yes --memcheck:leak-check=no --tool=memcheck -q --track-origins= root 861 420 0 00:13 pts/0 00:00:00 [sh] Eventually these processes use so much memory that the out of memory killer runs. Hide the tests that fail as a horrid work-around until the root cause has been resolved since this at least allows the ptest run to complete. This work-around is done in the run-ptest script using a sorted list of tests so that they can be easily restored one by one without a rebuild during testing. With core-image-minimal on qemuarm64: Recipe | Passed | Failed | Skipped | Time(s) valgrind | 333 | 49 | 17 | 7637 (From OE-Core rev: 208023f8fcbf4aee34544a80f962ae25f25ffb8d) Signed-off-by: Randy MacLeod Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

valgrind: ptest improvements to run-ptest and more

2019-09-16T22:02:44+00:00

Make some changes to the run-ptest script: - after main tests run integrity check like the pkg Makefile. - aesthetic and ordering changes Add the .in_place directory and its contents which allows valgrind to be run in-place thereby enabling the gdbserver_tests to complete rather than hang. Unfortunately directory paths embedded in binaries still cause many of these test to fail. Add the exp-sgcheck tests. With core-image-minimal on qemux86-64/kvm: Recipe | Passed | Failed | Skipped | Time(s) before | 648 | 12 | 60 | 1541 after | 662 | 20 | 38 | 1429 ppc-no-gdbserv | 415 | 196 | 34 | 10689 Since fewer tests timeout, the overall time has decreased. With core-image-sato on qemux86-64/kvm the results are now the same as core-image-minimal. qemuppc/arm64 runs result in the oom-killer eventually running since some processes do not terminate properly and accumulate as defunct processes in memory. Without the gdbserver_tests, the tests complete without defunct process or the oom-killer running for ppc but not for arm64. (From OE-Core rev: 6dbaaeec17eae8329031188b688b33306a871870) Signed-off-by: Randy MacLeod Signed-off-by: Ross Burton Signed-off-by: Richard Purdie