Bug#323996: xosview: Valgrind report use of unintialized values

2006-01-09 Thread Justin Pryzby
On Mon, Jan 09, 2006 at 11:49:53AM -0600, Gunnar Wolf wrote: > Ok, after asking some questions, I located the point Valgrind > complains at (line 92 of linux/diskmeter.cc): > > if (fields_[0] < 0.0) > > Now, this seems to be caused by certain confirguration of your system > or some actions yo

Bug#323996: xosview: Valgrind report use of unintialized values

2006-01-09 Thread Gunnar Wolf
Ok, after asking some questions, I located the point Valgrind complains at (line 92 of linux/diskmeter.cc): if (fields_[0] < 0.0) Now, this seems to be caused by certain confirguration of your system or some actions you took. Could you please provide some insight in order to reproduce this bu

Bug#323996: xosview: Valgrind report use of unintialized values

2006-01-09 Thread Justin Pryzby
On Mon, Jan 09, 2006 at 09:47:59AM -0600, Gunnar Wolf wrote: > tag 323996 + help > thanks > > Hi, > > Thanks for your report - which, I must admit, has spent too much time > waiting for my attention. > I understand the problems caused by using uninitialized values - but > am completely unfamili

Bug#323996: xosview: Valgrind report use of unintialized values

2006-01-09 Thread Gunnar Wolf
tag 323996 + help thanks Hi, Thanks for your report - which, I must admit, has spent too much time waiting for my attention. I understand the problems caused by using uninitialized values - but am completely unfamiliar with the valgrind tool, and cannot get much sense out of your report - Could

Bug#323996: xosview: Valgrind report use of unintialized values

2005-08-19 Thread Justin Pryzby
Package: xosview Severity: normal Version: 1.8.2-4 $ valgrind xosview ==6785== Memcheck, a memory error detector for x86-linux. ==6785== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al. ==6785== Using valgrind-2.4.0, a program supervision framework for x86-linux. ==6785== Copyright