libyuvTest_I420ToV210_OptVsC_Test valgrind error
GoogleCodeExporter opened this issue · comments
16:29:19 memcheck_analyze.py [ERROR] Command:
UninitCondition
Conditional jump or move depends on uninitialised value(s)
TestCpuFlag (/include/libyuv/cpu_id.h:42)
I420ToV210 (/source/convert_from.cc:648)
libyuv::libyuvTest_I420ToV210_OptVsC_Test::TestBody() (/unit_test/planar_test.cc:100)
Original issue reported on code.google.com by fbarch...@chromium.org
on 18 Sep 2012 at 6:02
r363 disables this test for now.
Original comment by fbarch...@google.com
on 19 Sep 2012 at 12:23
- Changed state: Started
Greetings,
When I re-enabled this test locally on my Core i7 PC and ran it, this error
happens when libyuv reads XGETBV+AVX bits, i.e. "(((cpu_info[2] & 0x18000000)
== 0x18000000) ? kCpuHasAVX : 0)". To read the source code of valgrind, it also
reads CPUID flags and sets hardware flags. Even though this is just a
hypothesis, valgrind may report errors when an application reads feature bits
not supported by the host PC?
Regards,
Hironori Bono
Original comment by hb...@google.com
on 16 Oct 2012 at 7:38
Re checked... no change
(view as text)
Suppression (error hash=#3C7A9BECB96AAF56#):
For more info on using suppressions see http://dev.chromium.org/developers/tree-sheriffs/sheriff-details-chromium/memory-sheriff#TOC-Suppressing-memory-reports
{
<insert_a_suppression_name_here>
Memcheck:Uninitialized
fun:InitCpuFlags
fun:MaskCpuFlags
fun:_ZN6libyuv33libyuvTest_I420ToV210_Invert_Test8TestBodyEv
}
Original comment by fbarch...@google.com
on 11 Jan 2013 at 11:56
Fixed in r536.
Original comment by fbarch...@google.com
on 12 Jan 2013 at 12:02
- Changed state: Fixed