]> code.ossystems Code Review - openembedded-core.git/commit
valgrind: fix memcheck vgtests remove fullpath-after flags
authorStacy Gaikovaia <Stacy.Gaikovaia@windriver.com>
Wed, 16 Sep 2020 23:23:04 +0000 (19:23 -0400)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 17 Sep 2020 08:47:16 +0000 (09:47 +0100)
commit9c82b9302c6ee84864e9a9cc870729395804e794
tree054e0546ce03ac7c03a54c3f16135508100b3edf
parent18ca377df98e53b84ae8ec9ba561392c776c10df
valgrind: fix memcheck vgtests remove fullpath-after flags

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>
meta/recipes-devtools/valgrind/valgrind/0001-memcheck-vgtests-remove-fullpath-after-flags.patch [moved from meta/recipes-devtools/valgrind/valgrind/0001-adjust-path-filter-for-2-memcheck-tests.patch with 52% similarity]
meta/recipes-devtools/valgrind/valgrind_3.16.1.bb