http://ftp.x.org/contrib/applications/xscreensaver-3.22.tar.gz

[xscreensaver] / README.debugging

diff --git a/README.debugging b/README.debugging
index f5ca66eb5b38d374a8d7158965f3d97699911a84..006fb5e392857ad7267227ac1bd4adfacb35d8a3 100644 (file)
--- a/README.debugging
+++ b/README.debugging
@@ -78,18 +78,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
+        *  If the problem is in the GUI, was it built using
            Motif, Lesstif, or Athena?  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 +118,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,12 +145,12 @@ 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.)
+           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
@@ -154,7 +161,7 @@ RUN-TIME PROBLEMS:
            you could start it from your login script like this (csh syntax):
 
               ( cd ~/src/xscreensaver/ ; \
-                xscreensaver -sync -verbose -timestamp -no-capture-stderr \
+                xscreensaver -sync -verbose -timestamp -no-capture \
                 >>&LOG & )
 
         *  Hackers only: If you're feeling adventurous enough to run gdb