On Monday, December 13th, 2021 at 1:12 AM, Dominik Vogt <dominik.v...@gmx.de> wrote: > On Sun, Dec 12, 2021 at 11:46:05PM +0000, Hegel3DReloaded wrote:
> > Sorry to say, but I even didn't have a chance to start after trying to log > > in. > > It crashes badly. Something to do with malloc and pointers. > > Should be fixed. We need test cases for all this parsing code. > > :-/ Since I'm using FVWM as a framework, my heaveweight configuration often triggers things. I'm not trying to promote my work, but having one VM with NsCDE and trying to run new FVWM code with it's setup can be a good "stress test". See my second mail on FvwmPager issue. It seems also as parsing issue: looks like window context for "Move" is lost. > I'm not very happy with the "new" monitor handling code. It added > potentially broken new parsing code all over the place. That > should really be done in a single, well tested parser. At the > moment we have a myriad of places where parsing is done, and its > very tedious to even execute all code paths. Is this has something to do with intensive work you and Thomas did couple weeks ago with new parser? -- Miroslav
