Douglas R. Reno wrote:
On Mon, Oct 31, 2016 at 5:34 PM, Bruce Dubbs <[email protected]> wrote:
I'm trying to update valgrind to version 3.12.0 for the book. The build
is fine, but I get over 1000 test failures.
I did rebuild a debug version of ld-2.24.so and that got a reduction to
166 test failures. It looks like there are a lot of issues with other
glibc libraries without debug symbols or just differences (4 bytes freed vs
8 bytes freed) in the latest glibc and/or kernel.
I'm looking for suggestions about how to handle this in the book.
I probably wouldn't have noticed this, as I have no desire whatsoever to
strip my libraries. I'm not concerned about size. Without stripped
libraries, I don't get as many failures, at least according to one of my
old logs.
We could do something about this in the valgrind page, but GDB goes through
the same thing. Do we really need to strip libraries?
The page in LFS Section 6.72 Stripping Again says that users not doing
debugging don't need to do it. A lot of users do not run tests and thus
do not have any problems. It mostly comes up for editors running tests
after building a new package version.
I suppose we could add role="nodump" to the xml in LFS
chapter06/strippingagain.xml so it is not picked up every time by jhalfs.
However, we still need to address the issue on the valgrind page in BLFS.
Since you have not stripped, can you do a quick check of
valgrind-3.12.0? The only thing I needs is ./configure && make && make
regtest.
There is a line that summarizes the tests. Mine looks like:
== 676 tests, 288 stderr failures, 66 stdout failures, 11 stderrB
failures, 13 stdoutB failures, 2 post failures ==
What do you get?
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
