On Sun, Feb 15, 2009 at 11:11:03PM +0000, Thomas Adam wrote: > 2009/2/15 Dominik Vogt <[email protected]>: > > I don't understand how putting a "return" after the > > "if (!FD_ISSET(...))" fixes your problem as the code that is > > executed inside the if block should always complete without > > waiting. > > Well, it's by no means fixed anything, but I've been running FVWM with > that change and not had a problem yet -- and normally by now I would > have, but I am willing to bet it's a red-herring. > > > I think you either running some bad module that crashes or hangs > > at random times, or a module that tries to send a synchronous > > command as a reaction to some fvwm message occuring about at the > > same time as the messages. The log message should tell you which > > module was killed. > > Unfortunately it doesn't tell me which module.
So what does it say? Can I have your config, please? > I am only running two > modules anyway: FvwmButtons and FvwmEvent, but I fail to see how > that's going to help (the only thing I could think of is that resizing > a window is sending ConfigureNotify requests out to most modules -- > but neither FvwmButtons or FvwmEvent would be explicitly reacting to > that -- especially in the case of FvwmEvent, I have nothing listening > on 'configure_window' for instance.) > > > To get a hold on the problem, I suggest you try to find out which > > messages fvwm and the module exchange. (Do we have some module > > message debugging code?). > > There's FvwmDebug which ought to help ascertain this. Note that I am > not the only one to report this problem, FWIW. See: > > http://fvwm.lair.be/viewtopic.php?f=6&t=2096&start=0 Uh, the module name is "/usr/bin/icedove"? That looks very strange indeed. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
