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

valgrind: Skip vgpreload_memcheck shared object from stripping

2019-01-08T20:14:44+00:00

This is a special library for memcheck tool, where it needs to have the symbols intact for the stack traces to work on target, current option is to install valgrind-dbg ( 151 MB uncompressed ) is quite big for some systems which may not have space to install it all. Leaving it unstripped adds about 200KB to image which is much better, this alone gets memcheck working, as an aside we might need same solution for other tools e.g. helgrind etc. when needed, they also have leading libraries installed (From OE-Core rev: 23da8f50b1e0a74777035c9f7b65b81456908f9f) (From OE-Core rev: 49e38e029a21c02ca44d6db1bc91190f7c6e11ca) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

valgrind: drop mips n32 support

2018-11-09T15:27:34+00:00

valgrind for qemumips64 multilib builds fails to configure for libn32 with the error: configure:6190: checking for 32 bit build support ... fatal error: bits/long-double-32.h: No such file or directory It seems that the toolchain is producing: tmp-glibc/sysroots-components/mips64-n32/libn32-glibc/usr/include/bits/long-double-n32.h Until the toolchain problem is resolved, skip valgrind for libn32. (From OE-Core rev: 17d5574f05384edeb5c80ada2724fff4a1c3c94b) Signed-off-by: Randy MacLeod Signed-off-by: Richard Purdie

valgrind: Make local functions static to avoid assembler error

2018-10-25T13:53:44+00:00

Avoid mips32 x-compiler warnings such as: | ../../../valgrind-3.14.0/helgrind/tests/annotate_hbefore.c:360:6: warning: no previous prototype for 'do_signal' [-Wmissing-prototypes] | void do_signal ( UWord* w ) | ^~~~~~~~~ by making functions and global variables that are file scope be static and more importantly also avoid an assembler error: /tmp/cce22iiw.s: Assembler messages: /tmp/cce22iiw.s:446: Error: symbol `exit_0' is already defined /tmp/cce22iiw.s:448: Error: symbol `exit' is already defined /tmp/cce22iiw.s:915: Error: symbol `exit_0' is already defined /tmp/cce22iiw.s:917: Error: symbol `exit' is already defined (From OE-Core rev: 5fface331c46b809c10b4f3d65904534d6933896) Signed-off-by: Randy MacLeod Signed-off-by: Richard Purdie

valgrind: update from 3.13.0 to 3.14.0

2018-10-20T21:40:16+00:00

The removed patches are all upstream. Adjusted two patches due to rebase. Guard against __GLIBC_PREREQ for musl libc (From OE-Core rev: 37841ec56d7756ec9ee00e2a2005681b220f6f5d) Signed-off-by: Randy MacLeod Signed-off-by: Richard Purdie

valgrind: fix compile ptest failure on mips32

2018-07-30T11:44:35+00:00

- Pass mips32's CFLAGS to tests - Fix broken inline asm in tests on mips32-linux - Build mips n32 successfully, support it. (From OE-Core rev: 23d9eba99d1180a0b859aadc23a10b391b8f6440) Signed-off-by: Hongxu Jia Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

valgrind: fix the shared object issue while prelink ptest

2018-04-13T15:58:07+00:00

If valgrind-ptest is installed, we will get the some prelink error like below at do_image: .../usr/sbin/prelink: /usr/lib64/valgrind/ptest/memcheck/tests/wrap7:\ Could not find one of the dependencies: \ .../usr/sbin//prelink-rtld: error \ while loading shared libraries: wrap7so.so: cannot open shared \ object file: No such file or directory The wrap7 needs to link the shared object in the path /usr/lib64/valgrind/ptest/memcheck/tests, but it fails. So we correct the path for ptest. (From OE-Core rev: 1ec0c977c55ae2c38252e1807dc15c56007d30dc) Signed-off-by: Zhixiong Chi Signed-off-by: Chen Qi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

valgrind: Fix multilib header conflict - valgrind/config.h

2018-03-15T13:27:19+00:00

Header file conflict between 32-bit and 64-bit versions. (From OE-Core rev: 6084879306db61c347b6f01f3bb64de327a9052d) Signed-off-by: Zhang Xiao Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

valgrind: Mask CPUID support in HWCAP on aarch64

2018-03-07T14:34:52+00:00

valgrind currently does not know anything about the CPUID flag added to the HWCAP auxv entry in kernel 4.11+ At runtime it will fails like this: ARM64 front end: branch_etc disInstr(arm64): unhandled instruction 0xD5380001 disInstr(arm64): 1101'0101 0011'1000 0000'0000 0000'0001 ==2082== valgrind: Unrecognised instruction at address 0x4014e64. This patch is a workaround by masking all HWCAP. This patch is dervied from https://bugzilla.redhat.com/show_bug.cgi?id=1464211 (From OE-Core rev: cdeb3d530af6cec1959c986aff3d6906939c8918) Signed-off-by: Manjukumar Matha Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

valgrind: improvements for run-ptest

2017-08-23T11:06:51+00:00

* Add statistic summary for run-ptest * Ensure the script can be run anywhere (From OE-Core rev: 8a6f5a2bc55975f38ad285ddea7122643b303c53) Signed-off-by: Jackie Huang Signed-off-by: Richard Purdie

valgrind: disable build for muslx32

2017-08-18T22:46:38+00:00

Disable build for muslx32.X32 isn't supported by valgrind at this moment. (From OE-Core rev: a945141062ac3d0736558be428f60af405b53a94) Signed-off-by: sweeaun Signed-off-by: Richard Purdie