Bug#358058: wmnetload: segfaults on startup
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
Bug#358058: wmnetload: segfaults on startup
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.
Thanks, Rogério Brito.
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#358058: wmnetload: segfaults on startup
Hi.
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.
What I *do* see, though, is that it, suddenly dies out of the blue,
when I'm using my system. My configuration is:
* sid, up to date (everyday);
* fluxbox;
* amd64, with 2 cores and bleeding-edge kernels from kernel.org.
Can we have any response to this thread? The bug has been filed for
quite some time, without *any* action being taken.
Thanks, Rogério Brito.
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#358058: wmnetload: segfaults on startup
I just installed wmnetload again and it seems to work for me now. I
haven't tested it extensively, but when I reported the bug (3 years
ago) it wouldn't start at all. I have to say that I pretty much lost
interest the moment it didn't work, but figured filing the bug might
be useful.
Now that I think about it, the server is entirely different now, so
perhaps this isn't too surprising. Still wmnetload 1.3-1.1 but now
basically all lenny, Linux turing 2.6.26-1-amd64 #1 SMP Fri Mar 13
17:46:45 UTC 2009 x86_64 GNU/Linux.
Scott
2009/4/9 Rogério Brito rbr...@ime.usp.br:
Hi.
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.
What I *do* see, though, is that it, suddenly dies out of the blue,
when I'm using my system. My configuration is:
* sid, up to date (everyday);
* fluxbox;
* amd64, with 2 cores and bleeding-edge kernels from kernel.org.
Can we have any response to this thread? The bug has been filed for
quite some time, without *any* action being taken.
Thanks, Rogério Brito.
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#358058: wmnetload: segfaults on startup
Package: wmnetload Version: 1.3-1.1 Severity: normal I just installed wmnetload via apt-get. When I type wmnetload to start it I just get Segmentation fault. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (600, 'testing'), (300, 'stable'), (200, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-k7-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages wmnetload depends on: ii libc6 2.3.6-3GNU C Library: Shared libraries an ii libdockapp2 1:0.5.0-1.3Window Maker Dock App support (sha ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte ii libxpm4 6.9.0.dfsg.1-4 X pixmap library wmnetload recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
