X-Git-Url: http://git.hungrycats.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=README.debugging;h=b0c140d3c6c946bf2b47301e246d47af7f087a47;hb=447db08c956099b3b183886729108bf5b364c4b8;hp=006fb5e392857ad7267227ac1bd4adfacb35d8a3;hpb=c596d1306f5f92f7eab76224d3b049980a14adcb;p=xscreensaver

diff --git a/README.debugging b/README.debugging
index 006fb5e3..b0c140d3 100644
--- a/README.debugging
+++ b/README.debugging
@@ -50,19 +50,13 @@ COMPILATION PROBLEMS:
         *  or pass $CC in the environment, like so:
 
               csh:  setenv CC cc ; ./configure
-              sh:   CC=cc ; ./configure
+              sh:   CC=cc ./configure
 
     Before doing this, you'll need to nuke `config.cache'.
 
-    If you get errors about not being able to find Motif or Athena (the
-    Xm/ or Xaw/ 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/ and Xaw/ (Athena) are free and available on all
-    systems; Xm/ (Motif) is available on all commercial systems except
-    SunOS 4.x and some early releases of Solaris.  For Linux and other
-    free Unixes systems, a Motif clone is 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 Athena?  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