invalid read in ipp_LoadLibrary

[mchibani]

Hi,

I'm using the H264 IPP based encoder under linux (ubuntu 7.10). When I check for memory leaks using valgrind, an invalid read is detected int the ipp_LoadLibrary module.

Is it something that we should worry about ?

Thanks

==3950==
==3950== Invalid read of size 4
==3950== at 0x4014BF3: (within /lib/ld-2.6.1.so)
==3950== by 0x4005BE9: (within /lib/ld-2.6.1.so)
==3950== by 0x4007A07: (within /lib/ld-2.6.1.so)
==3950== by 0x4010F83: (within /lib/ld-2.6.1.so)
==3950== by 0x400D015: (within /lib/ld-2.6.1.so)
==3950== by 0x401099D: (within /lib/ld-2.6.1.so)
==3950== by 0x415CC18: (within /lib/tls/i686/cmov/libdl-2.6.1.so)
==3950== by 0x400D015: (within /lib/ld-2.6.1.so)
==3950== by 0x415D2BB: (within /lib/tls/i686/cmov/libdl-2.6.1.so)
==3950== by 0x415CB50: dlopen (in /lib/tls/i686/cmov/libdl-2.6.1.so)
==3950== by 0x413CEDF: SysLoadLibary (in /opt/intel/ipp/5.3.1.062/ia32/sharedlib/libippsc.so.5.3)
==3950== by 0x413D01D: ipp_LoadLibrary (in /opt/intel/ipp/5.3.1.062/ia32/sharedlib/libippsc.so.5.3)

[Vladimir_Dudnik]

Hello,

automated test tools which work without access to source code may do mistakes analising binary. Usually that is ok. We test IPP against memory leak and see no issues here.

Thanks for reporting anyway.

Regards,
Vladimir

[mchibani]

Ok, Thanks