|
From: Gaetano M. <me...@gm...> - 2010-02-22 14:03:51
|
Hi all,
I have some tests that are not running with valgrind, digging in to it
I was able
to isolate the culprit code. The following test case is able
to reproduce the error:
#include <ipps.h>
int main() {
const int mySize = 1024;
Ipp32f* myRealVector = ippsMalloc_32f(mySize);
Ipp32f myResult = 0.0;
ippsStdDev_32f(myRealVector, mySize,
&myResult, ippAlgHintFast);
}
the function ippsStdDev_32f is a function in the Intel IPP library.
I'm running my test on a RedHat 5.4 64bit
Let me know if you need other informations.
Regards
Gaetano Mendola
--
cpp-today.blogspot.com
|
|
From: John R. <jr...@bi...> - 2010-02-22 15:55:38
|
> The following test case is able
> to reproduce the error:
>
> #include<ipps.h>
> int main() {
> const int mySize = 1024;
> Ipp32f* myRealVector = ippsMalloc_32f(mySize);
> Ipp32f myResult = 0.0;
> ippsStdDev_32f(myRealVector, mySize,
> &myResult, ippAlgHintFast);
> }
>
> the function ippsStdDev_32f is a function in the Intel IPP library.
> I'm running my test on a RedHat 5.4 64bit
Thank you for isolating that test case.
Please post a complete copy of the actual error message from valgrind.
The message contains several hexadecimal bytes which are
the actual instruction bytes which are not recognized.
Knowing those instruction bytes enables diagnosis and fixing
without requiring access to the Intel IPP library.
Not all developers have that library.
--
|