X-Git-Url: http://git.hungrycats.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=README.debugging;h=6afb2421dca24bfcb1239b4f98fb4d6356cd983a;hb=e4fa2ac140f7bc56571373a7b7eb585fa4500e38;hp=49755066102258ab23555e7b5fa8d9c36c68db87;hpb=06e9a7886a77cad92f9ddbc169d6d199a4d8b76d;p=xscreensaver

diff --git a/README.debugging b/README.debugging
index 49755066..6afb2421 100644
--- a/README.debugging
+++ b/README.debugging
@@ -54,15 +54,9 @@ COMPILATION PROBLEMS:
 
     Before doing this, you'll need to nuke `config.cache'.
 
-    If you get errors about not being able to find Motif or Gtk (the
-    Xm/ or gtk/ header files), and you can't find them on your system,
-    then your system is horked and your vendor is lame.  Perhaps the
-    problem is that you don't have some kind of ``development option''
-    installed.  Xt/is free and available on all systems; Xm/ (Motif)
-    is available on all commercial systems except SunOS 4.x and some
-    early releases of Solaris.  Linux and other free Unixes systems
-    usually come with Gtk, but a Motif clone is also available from
-    http://www.lesstif.org/.
+    If you get errors about not being able to find Gtk, then perhaps
+    the problem is that you don't have some kind of ``development
+    option'' installed.
 
 RUN-TIME PROBLEMS:
 
@@ -81,8 +75,8 @@ RUN-TIME PROBLEMS:
         *  Is the problem in the driver (`xscreensaver'), the GUI
            (`xscreensaver-demo'), or in the graphics hacks?
 
-        *  If the problem is in the GUI, was it built using
-           Motif, Lesstif, or Gtk?  Which version?
+        *  If the problem is in the GUI, was it built using Gtk, Motif,
+           or Lesstif?  Which version?
 
         *  If the problem is in one (or more) of the hacks, which ones?
            If you're not sure, try running `xscreensaver-demo' to go
@@ -152,17 +146,11 @@ RUN-TIME PROBLEMS:
            diagnostics; the `-no-capture' option prevents the data from being
            displayed on the screensaver window as well.)
 
-           You also might want to use the `-timestamp' option, which will
-           cause the xscreensaver messages to include the time at which
-           they were printed.
-
         *  If the problem is intermittent, you might want to capture the
            log information to a file and examine it later.  For example,
            you could start it from your login script like this (csh syntax):
 
-              ( cd ~/src/xscreensaver/ ; \
-                xscreensaver -sync -verbose -timestamp -no-capture \
-                >>&LOG & )
+               xscreensaver -sync -verbose -no-capture >>& saverlog &
 
         *  Hackers only: If you're feeling adventurous enough to run gdb
            on the xscreensaver driver process itself, make sure you've