summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/valgrind
AgeCommit message (Collapse)Author
2021-07-31valgrind: skip flaky ptest fb_test_amd64Tony Tascioglu
Recently, the none/tests/amd64/fb_test_amd64 test had been flaky and causing failures on the auto-builder. Until we can get to the root cause of the issue, we are going to skip the test to reduce the noise from the ptests. Signed-off-by: Tony Tascioglu <tony.tascioglu@windriver.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit a365cd7a358db96791033e6dc6e45d2e816d3e4c) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
2021-06-22valgrind: Actually install list of non-deterministic ptestsTony Tascioglu
Install list of non-deterministic threaded ptests to be run using taskset to force them to a single core. This commit works with b318944d7, which updated the testing script to run the non-deterministic tests separately but didn't install the list of tests, so these tests were being run without taskset. The taskset_nondeterministic_tests file is the list of tests that will be run separately with taskset, and ignored during the other tests. This is installed to /usr/lib/valgrind/ptest similar to the 2 existing lists for tests to skip on ARM and all architectures. Removed bar_bad and bar_bad_xml to be included separately as they cause issues on non-kvm QEMU instances. See: b318944dd7 valgrind: Improve non-deterministic ptest reliability for more info. Signed-off-by: Tony Tascioglu <tony.tascioglu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 3d23985d0d653844863ed513d75d93a36359992f) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
2021-06-22valgrind: remove buggy ptest from arm64Tony Tascioglu
This commit removes the stack_changes ptest from aarch64 devices. This test is buggy and fails almost 100% of the time in qemuarm64. In general, many of the valgrind tests are more likely to fail on qemuarm64 vs native x86_64. This test previously worked on gatesgarth and dunfell, but has been failing since hardknott. It might be due to a recent change in the cross-compiler or glibc. The test runs fine when running natively on arm on a Raspberry Pi. Until we can find the root cause for the failures, this shorter term solution should clear up some of the noise from the autobuilder from a known failure. Signed-off-by: Tony Tascioglu <tony.tascioglu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 82d6411b80a46d8ec0258ca75c3c80dc6128d44e) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
2021-06-10valgrind: Improve non-deterministic ptest reliabilityTony Tascioglu
Several of the valgrind tests (particulaly helgrind) are unreliable and can fail with a different output. Particularly, there is a higher chance of failure on QEMU instances with SMP enabled and on systems with more interrupts such as laptops on powersave. The tests have been reported upstream as being unreliable dating back over 5 years, due in part to the ordering of threads during an "unwinding" process in helgrind. https://bugs.kde.org/show_bug.cgi?id=345121 https://bugs.kde.org/show_bug.cgi?id=430321 A workaround to improve the reliability of such tests is to force them to run on a single CPU core using taskset. This greatly reduces the chance of a failure. >From my testing, I have found it can help reduce the rate of failures on both a laptop and QEMU by over 5x. Stress-testing in QEMU for several hours did not result in a failure while running the test normally did. The flaky or undeterministic thread-based tests are defined in the taskset_nondeterministic_tests file. These test cases will be run with taskset 0x00000001 to run on a single CPU core rather then the regular test. The edited run-ptest executes the flaky tests first, then ignores them to not duplicate the results from the main tests. Everything modified is restored when testing is complete. The drawback is that this isn't a foolproof solution. It helps the tests fail much less frequently, and considering how this issue has been documented for a long time, a workaround such as this is needed. Signed-off-by: Tony Tascioglu <tony.tascioglu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit b318944dd72ca7b0408e955f3599381ab3ac3ba8) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
2021-06-10valgrind: fix a typoKai Kang
Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 0478d9b04d6a6d10e439116b23b641a1e2553e26) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
2021-04-05valgrind: print failed ptest detailsYi Fan Yu
Some intermittent failures in valgrind are hard reproduce. Printing the difference between actual and expected will make understanding them slightly easier. [YOCTO #14294] Signed-off-by: Yi Fan Yu <yifan.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-03-23valgrind: Fix ptests on ppc64 LEKhem Raj
Backport a patch to avoid lsw/lmw instructions Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-03-10valgrind: Fix nlcontrolc.vgtestYi Fan Yu
Backport a recent upstream patch that redesigned the test. It's now enabled for both x86-64 and arm. [YOCTO #14223] Signed-off-by: Yi Fan Yu <yifan.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-27valgrind: Increase timeout duration 30 -> 90 sYi Fan Yu
Attempt to fix intermittent failure of `drd/tests/std_list` Locally tested to take around 45 s on qemuarm64 [YOCTO #14228] Signed-off-by: Yi Fan Yu <yifan.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-26meta/recipes-devtools: Add HOMEPAGE / DESCRIPTIONDorinda
Added HOMEPAGE and DESCRIPTION for recipes with missing decriptions or homepage [YOCTO #13471] Signed-off-by: Dorinda Bassey <dorindabassey@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-19valgrind: Remove reference to non-existent ptestsYi Fan Yu
exp-dhat: commit 441bfc5f5 promoted exp-dhat to dhat exp-sgcheck: commit 40187fcd6 removed the exp-sgcheck tool. Signed-off-by: Yi Fan Yu <yifan.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-18valgrind: Disable ptest nlcontrolc for x86-64Yi Fan Yu
Test hangs after glibc 2.33 uprev. Using gdb `p t[0]` to modify the timeout argument no longer affects how long `select` wait. https://bugs.kde.org/show_bug.cgi?id=432870 [YOCTO #14223] Signed-off-by: Yi Fan Yu <yifan.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-12-18valgrind: exclude bar_bad/bar_bad_xml from ptestsAlexander Kanavin
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. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-11-24valgrind: helgrind: Intercept libc functionsStacy Gaikovaia
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 Signed-off-by: Paul Floyd <paulf@free.fr> Signed-off-by: Stacy Gaikovaia <Stacy.Gaikovaia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-10-26valgrind: Fix build on musl after drd fixesRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-10-26valgrind: drd: fix pthread intercept test failuresStacy Gaikovaia
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. Signed-off-by: Stacy Gaikovaia <Stacy.Gaikovaia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-09-17valgrind: fix memcheck vgtests remove fullpath-after flagsStacy Gaikovaia
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. Signed-off-by: Stacy Gaikovaia <Stacy.Gaikovaia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-06-25valgrind: upgrade 3.16.0 -> 3.16.1Wang Mingyu
??Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-06-23valgrind: disable it for powerpc soft-floatValentin Longchamp
valgrind doesn't build for powerpc soft-float. It is thus disabled for such architectures. Signed-off-by: Valentin Longchamp <valentin@longchamp.me> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-06-04valgrind: upgrade 3.15.0 -> 3.16.0Wang Mingyu
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 <http://www.gnu.org/licenses/>. Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-05-18valgrind: Backport upstream patch to fix __getauxval needsKhem Raj
Drop disabling outline-atomics since that was added to fix this issue in particular Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-05-15valgrind: Do not use outline-atomics on aarch64Khem Raj
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 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-11valgrind: Fix timerfd syscall test to be 64bit time_t safeKhem Raj
This helps compile the testcase with musl on 32bit arches Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-02-23valgrind: exclude one more failing test for arm64Alexander Kanavin
valgrind's test suite isn't generally run by upstream on arm64, so let's simply disable the failing test and establish a set that works. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-02-23valgrind: replace a submitted patch with one that was mergedAlexander Kanavin
This addresses a ptest failure in particular that the submitted patch caused. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-02-02valgrind: Fix ptest builds on muslKhem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-02-02valgrind: fix the remaining ptest failuresAlexander Kanavin
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. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-16valgrind: partially fix ptestsAlexander Kanavin
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. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-12-30valgrind: Fix build with -fno-commonKhem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-16valgrind: disable 256 ptests for aarch64Randy MacLeod
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] <defunct> 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 Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2019-09-16valgrind: ptest improvements to run-ptest and moreRandy MacLeod
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. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2019-09-16valgrind: make a few more ptests passRandy MacLeod
Adjust two memcheck vgtest files to deal with relative paths that are in test executables when cross-compiling. Add libgomp to enable OpenMP tests. Add the bz2 executable for memcheck/tests/vcpu_bz2. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2019-09-16valgrind: enable ~500 more ptestsRandy MacLeod
Add valgrind's top level config.h to the ptest package since it is used by several scripts to determine which tests to run. Drop the removal of: none/tests/shell, the content was already moved to: none/tests/scripts/shell so the filter useless and the files no longer cause a problem. Add a few more test directories that had been omitted. Add perf/bigcode for test: none/tests/bigcode Leave .c, .h, .S files in the ptest image since several of them are needed to run the tests. The overhead is ~13 MB which is high but keeping all test code is easier than figuring out which source files are needed and the entire valgrind-ptest package is ~115 MB so in this context it's an acceptable trade-off. Add bash dependency for ptest for none/tests/scripts/shell With core-image-minimal on qemux86-64/kvm: Recipe | Passed | Failed | Skipped | Time(s) before | 149 | 1 | 9 | 663 after | 648 | 12 | 60 | 1541 Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2019-06-27valgrind: Remove dependency on libx11Adrian Bunk
It doesn't seem to be used. Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-05-21valgrind: add 'file' to ptest dependsRandy MacLeod
to avoid: ./run_openmp_test: line 12: /usr/bin/file: No such file or directory SKIP: drd/tests/omp_matinv when using core-image-minimal to run valgrind ptests. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-05-21valgrind: Make ptest timestamps copaseticRandy MacLeod
Avoid ptest failures due to .diffs such as cachegrind/tests/ann1.post.diff: @ Source file 'a.c' is more recent than input file 'cgout-test'. @ Annotations may not be correct. by using: touch a.c -r cgout-test Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-05-15valgrind: fix call/cachegrind ptestsRandy MacLeod
Use the *_annotate executables from ${bindir} Actually install cachegrind/tests/a.c since it is used by the call/cachegrind/tests/ann[12].vgtest files. With this change and the previous commits, the ptest results on qemux86-64 when invoked with: runqemu qemux86 kvm nographic slirp qemuparams="-m 2048" are: === Test Summary === TOTAL: 159 PASSED: 149 FAILED: 1 SKIPPED: 9 Only drd/tests/pth_detached3 remains to be fixed. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-05-15valgrind: adjust test filters and expected outputRandy MacLeod
Skip two filters in filter_xml_frames since they are intended to filter filesystem paths under '/usr' that vary from platform to platform. In the ptest case for Yocto's valgrind, the ptest executables are placed under: /usr/lib/valgrind/ptest and if these frames are filtered out, then several 'drd' tests fail the comparision between expected and actual output. Also adjust the std_list expected output to agree with that produced when the --yocto-ptest option to vg_regtest is used. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-05-15valgrind: update the ptest subdirs listRandy MacLeod
Split the list into one directory per line. Sort the list alphabetically. Add the gdbserver_tests directory to get the 'gone' executable which is needed by: memcheck/tests/gone_abrt_xml.vgtest Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-05-15valgrind: Include debugging symbols in ptestsRichard Purdie
About half the ptests will fail if the executables deployed as part of the ptest package are stripped. We therefore need to add a dependency on the dbg symbols package and silence the QA test which would complain about this since we really do want it in this case. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-05-15valgrind: fix vg_regtest return codeRandy MacLeod
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-04-23valgrind: update from 3.14.0 to 3.15.0Randy MacLeod
The SRC_URI moved. Two local patches are now fixed upstream so remove them. The glibc ptest results are essentially the same. 3.14 3.15 TOTAL: 579 589 PASSED: 297 301 FAILED: 251 254 SKIPPED: 31 34 DURATION: 1312 1171 Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-02-25valgrind: Mark powerpc64 with musl as incompatibleSerhey Popovych
Building musl for powerpc64 enforces elfv2 ABI since commit 68c964185519 ("arch-powerpc64.inc: Use elfv2 ABI when building with musl") that is not compatible with valgrind. Signed-off-by: Serhey Popovych <serhe.popovych@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-01-28valgrind: Dont strip off -mcpuKhem Raj
Defsault armtunes do not include -march any longer we habe -mcpu only, therefore to select right ISA we need to keep mcpu Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-01-03valgrind: Fix a race issue for libcoregrind.aRobert Yang
The libnolto_coregrind_a_OBJECTS is in libcoregrind_a_LIBADD, so the objects should be ready before generate libcoregrind.a, otherwise there would be failures: i586-poky-linux-ar: libnolto_coregrind_x86_linux_a-m_libcsetjmp.o: No such file or directory make[3]: *** [libcoregrind-x86-linux.a] Error 1 Add libnolto_coregrind_a_OBJECTS to EXTRA_libcoregrind_DEPENDENCIES to fix the problem. This is a race issue during parallel build. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-27valgrind: Fix x86_64 build failure with gcc9Khem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-05valgrind: Skip vgpreload_memcheck shared object from strippingKhem Raj
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 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-11-16valgrind: update upstream patch statusRandy MacLeod
Two recent patches are now marked as reported in the valgrind bugzilla. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-11-09valgrind: drop mips n32 supportRandy MacLeod
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. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-10-22valgrind: Make local functions static to avoid assembler errorRandy MacLeod
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 Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-26 19:47:11 +0000