> See if you can work out how to reproduce it at will and try it > against the new patch.
(... and now that I carefully planned to add the following before I sent the mail, and then completely didn't...) The MonitorLayout config var I just landed may be helpful in this; a hardcoded variant was the only way I managed to track down my crash in the first place. By using it to turn a Xnest into two side-by-side monitors, I could easily "fullscreen" an app, and have the other half of the nest easily visible to focus into/out of. Being able to flit the focus around like that, to the desktop or to other visible windows, makes it a lot easier to track down. As did being able to do it in a controlled environment like that, not by trying to crash the WM I'm actually having to _use_. Not just in not disrupting my work, but also having the debug output somewhere easy to fiddle with after it bombs out. (I also have this dream, that MonitorLayout can give us all the excuse we need to take VirtualScreens out back of the woodshed and shoot it in the head...) -- Matthew Fuller (MF4839) | [email protected] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
