The worst sort of bug is the sort that leads to a core dump/traceback map.
If this ever happens to you, please note down carefully what you were
doing.
If you are running Unix, please use dbx to examine the core file, and use
the where command; under VMS please note down the stack trace.
If dbx refuses to cooperate, please use the script `dump' in the main
directory, which uses adb to get at least some information.
Then send
the information to Robert Lupton or Patricia Monger.
If you can repeat the problem, use SAVE to save your killer programme,
and send it to one of us. Then we'll be able to RESTORE,
playback, and see the problem for
ourselves.(1)
If you don't complain, bugs won't get squashed.
The next class of problems are things that you don't like, or things that you would like to be able to do. Incomprehensible manuals come under this heading too. Please send them to us as well, and be as specific as possible. Please don't just say `the manual was awful' or or `Reading the manual was like my first exposure to James Joyce', but rather, `I found the manual hard to get into. More explanation of how to manipulate files of macros would have been useful, and more examples', or `I took 3 weeks to find how to draw logarithmic axes'.
Go to the first, previous, next, last section, table of contents.