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

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

In message <014a01c4a583$10e44270$0401a8c0@dan>
          "Daniel Miller \(IMI\)" <da...@im...> wrote:

> Okay, I added
> char xbuf = 0 ;
> to the beginning of get_number_of_luns().  I understand now that valgrind
> doesn't realize that xbuf will be initialized unless usb_control_msg()
> returned negative value, and in either case get_number_of_luns() will return
> a valid value.  So I'll have to add unnecessary initialization code to quiet
> valgrind, tho it isn't needed by the actual application.

You shouldn't need to do that as valgrind will monitor the code
in usb_control_msg() and should see xbuf being written to.

Tom

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