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,
+ If you get errors about not being able to find Gtk or Motif (the
+ gtk/ or Xm/ 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
+ 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/.
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 the it built using
- Motif, Lesstif, or Athena? Which version?
+ * If the problem is in the GUI, was it built using
+ Motif, Lesstif, or Gtk? 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
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'
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
projects / xscreensaver / blobdiff