Re: [wmii] snap: 20060309

From: David Tweed <>
Date: Thu, 9 Mar 2006 21:23:26 +0000 (GMT)

Whilst trying wmii I've managed to get a repeatable
crash that doesn't occur under other wm's (I've tried
Ion3) so I don't _think_ my program is doing anything

My program can be asked to open a list of files at
once and when doing this it opens (fltk) windows
relatively quickly. I've found that I can open up to
28 windows in one go ok, but when I try to open 55 at
one I get at some point after opening the windows wmii
crashes. If I first open 28 files, then open the
remaining 27 I don't get the crash. (The precise
numbers are just because I use regexps like "*.h" to
specify files; I'm trying to come up with a better way
to test this.) After a crash the XServer stderr log


X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.6.9-1.667 x86_64 [ELF]

Current Operating System: Linux lara 2.6.13-rc6 #1 Mon
Aug 15 08:08:57 BST 2005 x86_64
Build Date: 28 April 2005
        Before reporting problems, check http://wiki.X.Org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==)
default setting,
        (++) from command line, (!!) notice, (II)
        (WW) warning, (EE) error, (NI) not implemented, (??)
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Mar 9
18:48:21 2006
(==) Using config file: "/etc/X11/xorg.conf"

wmiiwm: fatal errorX Error of failed request:
BadValue (integer parameter out of range for
  Major opcode of failed request: 12
  Value in failed request: 0x0
  Serial number of failed request: 32526
  Current serial number in output stream: 32530

waiting for X server to shut down xterm: fatal IO
error 32 (Broken pipe) or KillClient on X server
xterm: fatal IO error 32 (Broken pipe) or KillClient
on X server ":0.0"
xterm: fatal IO error 32 (Broken pipe) or KillClient
on X server ":0.0"
xterm: fatal IO error 32 (Broken pipe) or KillClient
on X server ":0.0"


I've tried using a for loop in the shell opening
xterms and it can open 100 without problems, so I
suspect it's something more subtle than just the
number of opens.

If this is a new bug and it's relevant for fixing at
the current stage of wmii development, is there any
testing/debugging options I can use to provide more
info on what precisely its doing?

cheers, dave tweed

Yahoo! Photos NEW, now offering a quality print service from just 8p a photo
Received on Thu Mar 09 2006 - 22:23:27 UTC

This archive was generated by hypermail 2.2.0 : Sun Jul 13 2008 - 16:00:55 UTC