|
From: Thierry V. <val...@ea...> - 2005-09-13 14:02:07
|
Hello
I just have compiled valgrind-3.0.1 on a AMD-64 linux box
(with ./configure --prefix=/opt/valgrind)
Running valgrind as usual gives me the following error:
% /opt/valgrind/bin/valgrind --tool=addrcheck --trace-children=yes -v
--leak-check=full ls
Addrcheck is currently not working, because:
(a) it is not yet ready to handle the Vex IR and the use with 64-bit
platforms introduced in Valgrind 3.0.0
Sorry for the inconvenience. Let us know if this is a problem for you.
Output of uname -a:
===================
Linux macon.t-surf.com 2.4.21-9.0.3.ELsmp #1 SMP Tue Apr 20 19:44:29 EDT 2004
x86_64 x86_64 x86_64 GNU/Linux
The redhat version is:
======================
Red Hat Enterprise Linux WS release 3 (Taroon Update 3)
Did I miss something?
Thanks for your help
--
Thierry Valentin (val...@ea...)
Earth decision sciences SA (http://www.earthdecision.com)
22, Allée de la Foret de la Reine
54500 Vandoeuvre les Nancy, France
Phone: +33 (0)3-83-67-66-29
Fax: +33 (0)3-83-67-66-34
|
|
From: Tom H. <to...@co...> - 2005-09-13 14:13:05
|
In message <432...@ea...>
Thierry Valentin <val...@ea...> wrote:
> I just have compiled valgrind-3.0.1 on a AMD-64 linux box
> (with ./configure --prefix=/opt/valgrind)
>
> Running valgrind as usual gives me the following error:
>
> % /opt/valgrind/bin/valgrind --tool=addrcheck --trace-children=yes -v
> --leak-check=full ls
>
> Addrcheck is currently not working, because:
> (a) it is not yet ready to handle the Vex IR and the use with 64-bit
> platforms introduced in Valgrind 3.0.0
>
> Sorry for the inconvenience. Let us know if this is a problem for you.
Actually valgrind works fine on amd64. The addrcheck tool on the other
hand doesn't currently work on any platform with the 3.0.x valgrind
releases.
> Did I miss something?
Well mostly you seem to have failed to understand the message which
we added in 3.0.1 to explain that addrcheck is not available - perhaps
you have some suggestions on how we could make it clearer?
It would also be helpful to understand why you use addrcheck rather
than memcheck as there has been some debate as to whether it is
actually worth spending time to get it working again.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|