On Wed, 2013-10-16 at 10:48 -0700, Jerry Blakley wrote: > Thanks for the note. Here's the version I've been using: > > valgrind-3.8.1-15.fc19.x86_64 > > I wasn't able to find a more recent fedora package.
That is the latest stable version for f19. There are some newer versions for f20/rawhide, but I doubt they solve the issue. http://koji.fedoraproject.org/koji/packageinfo?packageID=98 > We run on servers at rackspace. There is an older generation of cpu's > and valgrind works find on them. It is the newer (about a year-old) > generation on which valgrind doesn't work. This was a big surprise, > since I think they are stock processors. Might there be something in > the VM/hypervisor layer which is not translating correctly? > > > I did just go the svn route. The results look similar. Then it at least isn't the fedora package/patches. Thanks for checking. So it must be some flag/cpuid combination valgrind isn't handling correctly. Would you mind installing cpuid (it is packaged for fedora) or building it from source: http://etallen.com/cpuid.html Then run: cpuid -1 and cpuid -1 -r Please file that output in a new bug at: https://bugs.kde.org/enter_bug.cgi?product=valgrind Thanks, Mark ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
