|
From: Julian S. <js...@ac...> - 2006-01-21 02:29:21
|
Dave
> but in the offical release valgrind -v output the error messages are
> generated before reading in libc.2.3.4.so I thought the problems I was
> seeing might be related to the fact that the libc archive was read in
> too late.
The default suppressions are quite fragile, because there's a wide
variability in the number of symbols attached to libc.co and ld.so,
depending on the Linux distro you're using. I'd hazard a guess that
you're using SLES9, which is a distro we didn't test 3.1.0 on as
we didn't have access to a machine running it.
> If you think this analysis is correct, then my suggested fix for this is
> to add an additional entry in glibc-2.3.supp:
> -{
> - index-not-intercepted-early-enough-HACK-4
> - Memcheck:Cond
> - fun:index
> - fun:expand_dynamic_string_token
> -}
Seems reasonable.
--------
By far the most effective way to ensure V works well on your
system is to set up the nightly build system on it. Monitoring
and fixing failures the nightly builds report to the dev list
really helps keep the system working well.
It's easy:
check out from svn, copy the nightly/ directory somewhere else
and read nightly/README.txt. This will do builds of the svn trunk
and sometimes picks up stuff which should be merged to the stable
(3.1.X) branch.
J
|