Bug#388702: sawfish: Invalid use of setitimer() reported in syslog
Package: sawfish Version: 1:1.3+cvs20060518-3 Severity: normal I noticed the following error messages in syslog: Sep 21 23:58:33 tirith kernel: setitimer: sawfish (pid = 15117) provided invalid timeval it_value: tv_sec = 59 tv_usec = 100 Sep 22 00:01:31 tirith kernel: setitimer: sawfish (pid = 15117) provided invalid timeval it_value: tv_sec = 59 tv_usec = 100 Looks like it should have been tv_sec == 60 and tv_usec == 0. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-amd64-k8-tirith Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages sawfish depends on: ii eterm [x-terminal-em 0.9.3-1 Enlightened Terminal Emulator ii gnome-terminal [x-te 2.14.2-1The GNOME 2 terminal emulator appl ii libatk1.0-0 1.12.2-1The ATK accessibility toolkit ii libaudiofile00.2.6-6 Open-source version of SGI's audio ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii libcairo21.2.4-1 The Cairo 2D vector graphics libra ii libesd0 0.2.36-3Enlightened Sound Daemon - Shared ii libfontconfig1 2.3.2-7 generic font configuration library ii libglib2.0-0 2.12.3-2The GLib library of C routines ii libgmp3c22:4.2.1+dfsg-4 Multiprecision arithmetic library ii libgtk2.0-0 2.8.20-1The GTK+ graphical user interface ii libice6 1:1.0.1-2 X11 Inter-Client Exchange library ii libpango1.0-01.12.3-1+b1 Layout and rendering of internatio ii librep9 0.17-13 lisp command interpreter ii libsm6 1:1.0.1-2 X11 Session Management library ii libx11-6 2:1.0.0-8 X11 client-side library ii libxcursor1 1.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxfixes3 1:3.0.1.2-4 X11 miscellaneous 'fixes' extensio ii libxft2 2.1.8.2-8 FreeType-based font drawing librar ii libxi6 1:1.0.1-3 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library ii libxrender1 1:0.9.1-3 X Rendering Extension client libra ii rep-gtk 0.18.cvs20060518-2 GTK binding for librep ii rxvt [x-terminal-emu 1:2.6.4-10 VT102 terminal emulator for the X ii sawfish-data 1:1.3+cvs20060518-3 sawfish architecture independent d ii xterm [x-terminal-em 210-3 X terminal emulator sawfish recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388702: sawfish: Invalid use of setitimer() reported in syslog
tag 388702 moreinfo thanks On Fri, Sep 22, 2006 at 01:05:23AM -0400, Per Bojsen wrote: > I noticed the following error messages in syslog: > > Sep 21 23:58:33 tirith kernel: setitimer: sawfish (pid = 15117) provided > invalid timeval it_value: tv_sec = 59 tv_usec = 100 > Sep 22 00:01:31 tirith kernel: setitimer: sawfish (pid = 15117) provided > invalid timeval it_value: tv_sec = 59 tv_usec = 100 > > Looks like it should have been tv_sec == 60 and tv_usec == 0. I'm sorry, I can't reproduce this. Do you have some external lisp add on? You could try tracing: 1. Start sawfish from a terminal. Don't background it 2. On another terminal run sleep 5; sawfish-client -e "(trace 'set-timer)" then return focus to the sawfish terminal *before* the 5 seconds. 3. Whenever any timer is restarted, sawfish should drop into the debugger, where you can get a backtrace and see what function is using the timer. -- Rodrigo Gallardo GPG-Fingerprint: 7C81 E60C 442E 8FBC D975 2F49 0199 8318 ADC9 BC28 signature.asc Description: Digital signature
Bug#388702: sawfish: Invalid use of setitimer() reported in syslog
*** Regarding Re: Bug#388702: sawfish: Invalid use of setitimer() reported in syslog; Luis Rodrigo Gallardo Cruz <[EMAIL PROTECTED]> adds: Luis> I'm sorry, I can't reproduce this. Do you have some external Luis> lisp add on? No, I don't think so. I have not seen the problem in a while. I suspect it happens only in response to certain rarely used activity. It looks a bug in the code that calculates a delay that does not correctly handle carry. It obviously meant to set the itimer to 60s but ended up asking for 59s and 100us. I was hoping this could be found by inspecting the code since we know it has to do with setitimer. I haven't had a chance to look into it more closely. Per -- Per Bojsen <[EMAIL PROTECTED]> 7 Francis Road Billerica, MA 01821-3618 USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
