On Monday, June 14, 2010, Thomas Rast wrote:
Sorry, I should have quoted the link, I had it in the original post:
http://bugs.kde.org/show_bug.cgi?id=215914
The symptomps match so I think it's this bug.
Please could you add your analysis and patch to the above URL.
Bug reports and fixes
On Mon, Jun 14, 2010 at 5:28 PM, Robert Berger
robert.karl.ber...@gmail.com wrote:
It looks like last time this mail did not make it to the list.
Here I try again.
Hi Robert,
Does the current Valgrind trunk build and install fine on your setup ?
Cross-compilation should work again with the
Hi Bart,
On 06/15/2010 06:10 PM, Bart Van Assche wrote:
Hi Robert,
Does the current Valgrind trunk build and install fine on your setup ?
Cross-compilation should work again with the current trunk.
It looks like cross compilation is up and running again. Cool!
svn co
On Tue, Jun 15, 2010 at 5:55 PM, Robert Berger
robert.karl.ber...@gmail.com wrote:
[ ... ]
That's what my target says:
-bash-3.2# valgrind
valgrind: failed to start tool 'memcheck' for platform 'ppc32-linux': No
such file or directory
-bash-3.2#
You can analyze what went wrong by
My x86 (ie. 32 bit) code was calculating numbers differently when run by itself
(A) than when run thru valgrind (V). This is numerically intensive code so I'm
certain the differences are in the floating point calculations. I understood
that this could be due to the differences in floating
My x86 (ie. 32 bit) code was calculating numbers differently when run
by itself (A) than when run thru valgrind (V). This is numerically
intensive code so I'm certain the differences are in the floating point
calculations. I understood that this could be due to the differences in
floating point
On 06/15/2010 07:05 PM, Bart Van Assche wrote:
On Tue, Jun 15, 2010 at 5:55 PM, Robert Berger
robert.karl.ber...@gmail.com wrote:
[ ... ]
That's what my target says:
-bash-3.2# valgrind
valgrind: failed to start tool 'memcheck' for platform 'ppc32-linux': No
such file or directory
I've had the same problem, but saw a colleague using DESTDIR when
building some other project (See the make install command). This also
works with valgrind. I build valgrind with this script:
**
export location=$(pwd)
#Path to compiler:
export
