Rogério Brito ha scritto: > Hi again, > > On Apr 09 2009, Rogério Brito wrote: >> On May 27 2008, Alexandre Lymberopoulos wrote: >>> The program causes a segmentation fault when X starts and the device >>> to be monitored is not up. When the monitored device is up wmnetload >>> seems to work perfectly. >> I'm also seeing the segfaults, but I can't pinpoint when they happen >> precisely. I have many interfaces and sometimes they are working, >> sometimes not and wmnetload seems to work ok. > > Upon further investigation, it seems that wmnetload doesn't cycle > between all interfaces when the right mouse button is clicked on the > dock app. > >> What I *do* see, though, is that it, suddenly dies "out of the blue", >> when I'm using my system. My configuration is: > > I'm still seeing such problems, but now I've run it through valgrind and > I see many messages of the type: "conditional jump or move based on > unitialized value, blah, blah". > > Also, I found an unitialized variable being used. The source for that > was a typo. In file wmnetload.c::approxpixel, the following snippet of > code is wrong: > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > diffr = (red - colorcells[i].red) >> 8; > diffg = (green - colorcells[i].green) >> 8; > diffr = (blue - colorcells[i].blue) >> 8; > > approx = diffr * diffr + diffg * diffg + diffb * diffb; > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > Obviously, the variable corresponding to the blue color is diffb, not > diffr. This fixes one problem. > > There are also other initialization problems regarding wrong number of > initializers for structures. > > Also, some signed vs. unsigned comparisons are made in the c files. > >> Can we have any response to this thread? The bug has been filed for >> quite some time, without *any* action being taken. > > Lorenzo, are you listening? Please, reply. I fear that some drastic > measures would be necessary if we *continue* to have no feedback from > you.
Hi guys, sorry for the long silence. I'm currently not able to reproduce the bug. I tried to start wmnetload with different interfaces and to bring up and down these interfaces manually but I did not experience any crash. Valgrind reports the same warnings noticed by Rogério. I'm running wmnetload through gdb and waiting the segfault. Are you aware of any deterministic trigger for the segfault? Lorenzo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
