X-Git-Url: http://git.hungrycats.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=README.debugging;h=b0c140d3c6c946bf2b47301e246d47af7f087a47;hb=3f438031d610c7e15fd33876a879b97e290e05fb;hp=f5ca66eb5b38d374a8d7158965f3d97699911a84;hpb=2a991a811de4c7b22f812682b267b616a809fd9a;p=xscreensaver

diff --git a/README.debugging b/README.debugging
index f5ca66eb..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:
 
@@ -78,18 +72,15 @@ RUN-TIME PROBLEMS:
         *  What platform are you running on?  What does the included
            `./config.guess' shell script print?
 
-        *  Is the problem in the driver, or in the graphics hacks?
+        *  Is the problem in the driver (`xscreensaver'), the GUI
+           (`xscreensaver-demo'), or in the graphics hacks?
 
-        *  If the problem is in the driver, was the driver 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
-
-              xscreensaver-command -demo
-
-           to go through the list of them and see which work and which
-           don't.
+           If you're not sure, try running `xscreensaver-demo' to go
+           through the list of them and see which work and which don't.
 
         *  Does the problem occur when running that hack by hand, in
            its own window (i.e., when started with no command-line args)?
@@ -121,8 +112,18 @@ RUN-TIME PROBLEMS:
               where
 
            If the bottom few lines of the output don't include the functions
-	   `main_loop()' and `main()', then something's wrong: are you sure
-           the core file came from that program?
+           `main_loop()' and `main()', then something went wrong, and the
+           core file is bogus.  If the lines it prints out contain only
+           question marks, then the core file is bogus.  Are you sure the
+           core file came from that program?  Did you compile with -g, as
+           explained above?  If you don't compile with -g, the core file
+           won't have any information in it.
+
+           Never ever ever mail me (or anyone) a core file.  They are huge,
+           and are only meaningful on the machine that generated them, with
+           the exact executable that generated them, neither of which anyone
+           but you has access to.  Don't mail me a core file unless you're
+           also planning on mailing me your computer.
 
         *  If it gets an X error, where did it come from?  Run
            xscreensaver with the `-sync' command-line option.  When `-sync'
@@ -138,24 +139,18 @@ RUN-TIME PROBLEMS:
 
         *  Start `xscreensaver' with the command-line arguments
 
-              -verbose -no-capture-stderr
+              -verbose -no-capture
 
            This will cause it to write a lot of debugging info to the stderr
            of the xscreensaver process (the `-verbose' option turns on the
-           diagnostics; the `-no-capture-stderr' 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.
+           diagnostics; the `-no-capture' option prevents the data from being
+           displayed on the screensaver window as well.)
 
         *  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-stderr \
-                >>&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