In message <[EMAIL PROTECTED]> on Wed, 16 Jun 2004 20:07:52 +0200, "Zvi Har'El via RT" <[EMAIL PROTECTED]> said:
ctwm-bugs> The effect was disasterous: ctwm-bugs> ctwm-bugs> /usr/local/src/build/ctwm$ ./ctwm ctwm-bugs> ctwm-bugs> Congratulations, you have found a bug in ctwm ctwm-bugs> If a core file was generated in your directory, ctwm-bugs> can you please try extract the stack trace, ctwm-bugs> and mail the results, and a description of what you were doing, ctwm-bugs> to [EMAIL PROTECTED] Thank you for your support. ctwm-bugs> ...exiting ctwm now. ctwm-bugs> ctwm-bugs> zsh: abort ./ctwm ctwm-bugs> ctwm-bugs> No core dump was generated... Hmm, so we end up with mutual dependencies between ConfigureWorkSpaceManager() and ParseTwmrc(). Charming... The problem, as it happens, is that it's the code called by ParseTwmrc that sets Scr->workSpaceMgr.initialstate, and ConfigureWorkSpaceManager() uses that value to initialise the state in each virtual screen. At the same time, there is code called by ParseTwmrc() that depends on all virtual screens have a window manager window, which are created by ConfigureWorkSpaceManager(). There's definitely a bit of cleanin to do... ----- Please consider sponsoring my work on free software. See http://www.free.lp.se/sponsoring.html for details. -- Richard Levitte | http://richard.levitte.org/ | Tunnlandsv. 52 Levitte Programming | http://www.lp.se/ | S-168 36 Bromma T: +46-708-26 53 44 | | SWEDEN "Price, performance, quality... choose the two you like"
