Comment 3 for bug 2051421

I've fixed a few things upstream, and now get

== 720 tests, 20 stderr failures, 4 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==

Two things aren't simple to deal with. The varinfo failures are due to not being able to read the debuginfo related to local variables. I don't know if that is a Valgrind bug or a GCC/ARM limitation. It's not a big problem, just makes the error messages a bit less clear. helgrind/tests/hg05_race2 is in the same boat.

There seems to be some issue with the 'newarray' leak detection heuristic. Again not too serious, it just changes how detected leaks get categorized.

The above two are the main ones that affect users.

I still have a number of failures related to CPU features. I need to improve the autoconf configure script to improve that, and also add compiler switches on a case by case basis for specific tests.

I need to look at memcheck/tests/sem to see exactly which bit of memory is triggering the spurious looking error.

The other errors all look fairly cosmetic.