On Thu, 24 Aug 2000, Nathan Clemons [SYS] wrote:
> I'll also configure 0.61.0 with debugging on and try to get an idea of
> what's going on that way. More info is better, obviously. :)
>
> --Nathan
>
DEBUG mode doesn't give a lot of info... my
~/.dt/sessionlogs/phoenix_DISPLAY=:0 says:
-- Session log created Thu Aug 24 12:55:45 EDT 2000
OpenWindows Desktop Login
using xinitrc file: /home/staff/nathan/.xinitrc
BScreen::BScreen: managing screen 0 using visual 0x2a, depth 24
BScreen::BScreen: managing screen 0 using visual 0x51280, depth 331776
BScreen::BScreen: managing screen 0 using visual 0x51d58, depth 334848
/home/staff/nathan/bin/blackbox: signal 15 caught
shutting down
Went to enable debug mode on 0.51.3.1, but it doesn't have that.
It seems odd that it first sees the depth as 24, then gets confused and
things it's depth 331776, then 334848. If I send it a SIGHUP or SIGUSR2,
it repeats the 0x51d58 (consistantly).
I added a few statements in the code to tell me if it enabled the slit
(which it didn't), or if it finished loading the menu (which it didn't).
diff -c Screen_old.cc Screen.cc
*** Screen_old.cc Thu Aug 24 13:03:50 2000
--- Screen.cc Thu Aug 24 12:51:34 2000
***************
*** 434,439 ****
--- 434,450 ----
#ifdef SLIT
slit = new Slit(this);
+
+ fprintf(stderr,
+ i18n->
+ getMessage(
+ #ifdef NLS
+ ScreenSet, ScreenManagingScreen,
+ #else // !NLS
+ 0, 0,
+ #endif // NLS
+ "BScreen::BScreen: enabling slit on screen %d\n"),
+ getScreenNumber());
#endif // SLIT
InitMenu();
***************
*** 1840,1845 ****
--- 1851,1868 ----
BScreen::Exit);
} else
blackbox->saveMenuFilename(blackbox->getMenuFilename());
+
+
+ fprintf(stderr,
+ i18n->
+ getMessage(
+ #ifdef NLS
+ ScreenSet, ScreenManagingScreen,
+ #else // !NLS
+ 0, 0,
+ #endif // NLS
+ "BScreen::BScreen: loaded menu on screen %d\n"),
+ getScreenNumber());
}
Hope this gives a better idea of the problem.
--Nathan
