Comment # 2 on bug 932306 from
Created attachment 635465 [details]
valgrind log

some libstorage things:

Conditional jump or move depends on uninitialised value(s)
   at 0x88FD78B: rb_obj_written (ruby.h:1269)
   by 0x88FD78B: rb_obj_write (ruby.h:1291)
   by 0x88FD78B: rb_ary_push (array.c:910)
   by 0x1B0EEFDC: SWIG_Ruby_AppendOutput (storage_wrap.cxx:1335)
   by 0x1B114E96: _wrap_createStorageInterfacePid(int, unsigned long*, unsigned
long) (storage_wrap.cxx:31474)
   by 0x8A43EED: vm_call_cfunc_with_frame (vm_insnhelper.c:1382)
   by 0x8A43EED: vm_call_cfunc (vm_insnhelper.c:1475)
 Uninitialised value was created by a stack allocation
   at 0x8A40EE0: call_cfunc_m1 (vm_insnhelper.c:1209)

Conditional jump or move depends on uninitialised value(s)
  at 0x69667F9: std::num_put<char, std::ostreambuf_iterator<char,
std::char_traits<char> > >::do_put(std::ostreambuf_iterator<char,
std::char_traits<char> >, std::ios_base&, char, bool) const (in
/usr/lib64/libstdc++.so.6.0.19)
  by 0x697294E: std::ostream& std::ostream::_M_insert<bool>(bool) (in
/usr/lib64/libstdc++.so.6.0.19)
  by 0x1B621FB7: operator<< (ostream:175)
  by 0x1B621FB7: storage::operator<<(std::ostream&, storage::FsCapabilities
const&) (StorageTypes.cc:176)
  by 0x1B5B80A9: storage::Volume::changeMountBy(storage::MountByType)
(Volume.cc:740)
  by 0x1B52BC03: storage::Storage::changeMountBy(std::string const&,
storage::MountByType) (Storage.cc:2637)
  by 0x1B1072C0: _wrap_StorageInterface_changeMountBy(int, unsigned long*,
unsigned long) (storage_wrap.cxx:25305)
  by 0x8A43EED: vm_call_cfunc_with_frame (vm_insnhelper.c:1382)
Uninitialised value was created by a stack allocation
  at 0x1B50AB70: ??? (in /usr/lib64/libstorage.so.6.0.0)

For the second one, apparently Volume::changeMountBy will log the value of an
uninitialized `caps` if `getFsCapabilities` fails. (Actually it
seems the logging is disabled, but the string is constructed
anyway.)


You are receiving this mail because: