Blair Zajac wrote:
Nuutti Kotivuori wrote:
Blair Zajac wrote:
Do you get simple errors like these? I'm on RedHat 8.0
[...]
It's not too easy to debug when you have errors like these on
the most simple of commands.
That kind of errors arise when the valgrind suppression file is not
up to date with the system, the compiler and libc. The simple
answer is: blame RedHat.
Don't you mean to blame valgrind, as RedHat 8.0 doesn't come with
valgrind? Also, I'm using valgrind 1.9.3, which you'd figure would
handle RedHat 8.0 without errors.
Um, every time I take valgrind from one machine and move it to
another, I get similar spurious errors. Every time the libc changes,
but valgrind doesn't, I get similar errors.
The suppression file must be kept in sync with the system valgrind is
running on, taking account the system's versions of different system
libraries. 'valgrind' cannot do this for every linux distribution
available, especially not for distributions that are often
updated. It's the package maintainers job to keep it in sync on the
distribution he provides binary packages for.
But, since RedHat 8.0 doesn't come with 'valgrind', I am assuming you
mean you compiled it yourself - in which case you should should fix
the suppression file. Luckily it's rather easy:
# Format of this file is:
# {
# name_of_suppression
# kind: one of Param Value1 Value2 Value4 Value8
# Free Addr1 Addr2 Addr4 Addr8
# Cond (previously known as Value0)
# (if Param: name of system call param, if Free: name of free-ing fn)
# caller0 name, or /name/of/so/file.so
# caller1 name, or ditto
# (optionally: caller2 name)
# (optionally: caller3 name)
# }
For example, Debian's valgrind offers different suppressions files for
different Debian releases directly - some of which would be relevant
here directly.
-- Naked
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:06:04 2006