Re: [Valgrind-users] improbably "uninitialized value" warning

[Tom H. <th...@cy...>]

In message <Xns95726316C156Fdancarddupercom@80.91.229.5>
          Daniel Miller <da...@im...> wrote:

> I'm using valgrind 2.2.0 for the first time, on a linux 2.6.7 system with
> gcc 3.3.4.  I have optimizations set to -O.  However, I'm getting *many*
> warnings about "Conditional jump or move depends on uninitialized value"...
> some of these warnings are clearly spurious; a typical example is:
> 
>    result = get_number_of_luns(udev) ;
>    total_luns = (result <= 0) ? 1 : result ;  //  line 1449
> 
> ==25533== Conditional jump or move depends on uninitialised value(s)
> ==25533==    at 0x805AC84: find_dev_cap(unsigned) (imilib.cpp:1449)
> 
> result is defined as int, and get_number_of_luns() returns int.  So result
> cannot be uninitialized here.

It can be uninitialised ig get_number_luns() returns a value
that is not properly initialised.

Tom

-- 
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/