|
From: Julian S. <js...@ac...> - 2005-11-20 22:03:32
|
Release candidates for Valgrind 3.1.0, and a matching version of Callgrind, 0.10.1, are available at: http://www.valgrind.org/downloads/valgrind-3.1.0RC1.tar.bz2 http://www.valgrind.org/downloads/callgrind-0.10.1RC.tar.gz A matching version of the Valkyrie GUI and associated XML tools will be available for 3.1.0 final. This release works on {x86,amd64,ppc32}-linux. The main changes are greatly improved AMD64 support, better memory management, and fully integrated support for 32-bit PowerPC. There are many refinements and bug fixes. See NEWS in the sources for more details. Please download and test it. We would be especially pleased to hear from people with less-mainstream setups, especially if: - you run Linux on PowerPC - you have an older x86 distro. 3.1.0 should work on a vanilla RedHat 7.3 setup. However, our ability to test on old LinuxThreads setups is gradually declining. - your application uses large amounts of memory. 3.1.0 can utilise all available address space on 32-bit targets, and up to 32GByte on amd64. - you use exotic/obscure/non-mainstream functionality of Valgrind. To build, first build Valgrind in the normal way: cd valgrind-3.1.0RC1 ./configure --prefix=... make make install Then you can untar and build callgrind: cd callgrind-0.10.1RC ./configure --prefix=... (same prefix as above) make install $PREFIX/valgrind --tool=callgrind ls Known issues, which will be fixed in 3.1.0 final: - Due to a bug in the build system, you must do 'make' and then 'make install' to get a V install tree against which callgrind is buildable. ('make install' by itself works fine for building V). - The tarball contains two Altivec test programs (for ppc32). Due to a packaging oversight these are not run at 'make regtest' time. J |