I have experienced several seg faults of Window Maker while testing 5.9.9 Sparc. The following was returned to the console: [jkotran@george ~]% X connection to :0.0 broken (explicit kill or server shutdown). wmaker warning: got signal 1 (Hangup) - exiting... wmaker fatal error: got signal 11 (Segmentation fault) wmaker fatal error: a fatal error has occured, probably due to a bug. Please fill the included BUGFORM and report it. wmaker warning: trying to start alternative window manager... wmaker fatal error: got signal 11 (Segmentation fault) wmaker fatal error: crashed while trying to do some post-crash cleanup. Aborting immediatelly. I was not trying to start an alternative window manager. I am not sure why the message states that. I was moving a windows at the time of the crash. Joe Kotran
The "connection to X server lost" message is a clue to me that what actually happened was that the X server died, and once X went away this is what confused the crap out of windowmaker and caused it to subsequently core. The "received HUP signal" is yet another clue that what in fact happened was that the X server died on him. I've tried to reproduce X crashes on sparc32 with recent builds, but with all of them I was able to make happen, each time it was due to an out of memory condition because I had opened up so many GNOME applications on a low memory machine. This was verified by watching 'free' output at the time of the crash and seeing swap space completely filled. Is it possible to find out what machine type this happened on? (what's important is "sun4c/sun4m/ultrasparc", amount of RAM, and type of video card)
The machine that I was testing Red Hat 5.9.9 Sparc has the following specifications: Sparc 5/100 (sun4m) 128 MBytes RAM 64 MBytes swap cgsix frame buffer I did not seem significant at the time, but yes I was running GNOME applications. Specificially gnorpm seems to cause the X server to crash every time I run it under WindowMaker. Joe Kotran
This should be fixed with the egcs/kernel sparc errata.