Nadim Shaikli spake unto us the following wisdom: > > Maybe. But I would try to narrow the "#if 0" code even more so that there > > is still no problem. > > That would be interesting to see. Ideally it would be wonderful to > simply run fvwm and this code under a debugger and single step around > for a better feel for what is causing it to go into the weeds. In any > regard, I'm all ears :-)
How about running your debugger/fvwm in a screen session? You can
then connect to that screen session once X is started up and work from
there, and if it bombs out you can restart X and connect to the
crashed session for some post-mortem analysis.
Ethan
--
And if I claim to be a wise man / it surely means that I don't know.
-- Kansas, "Carry on Wayward Son"
pgpGfz2vPBX7x.pgp
Description: PGP signature
