Bug Reports

[ This page has been created very quickly to show you what I instantly feel I will need to be able to find a bug from your reports. It will be revised when I've given it more thought. ]

I receive bug reports on my GNU ports from several people, and I've noticed that the quality varies a lot, and I keep asking for more information all the time. This page will tell you what I would like to receive from you when you send me a bug report:

• Information on what compiler is used (including version), what TCP/IP kit is used (if applicable, and including version), what version of DECWindows is used (if applicable), and the version of VMS on which the build is done. If I've missed something, just add that too.
• In the case of Emacs, the creation date of the latest upgrade kit you have applied.
• The configuration command, and the values of the logical names that have been used in the values to --prefix and friends.
• The MMS or MMK command that was used to build and to install Emacs (Well, if you haven't installed it yet, just say so)
• The exact key sequence that lead to the error in question, at least if inside Emacs. I know that it's sometimes difficult, and if it's impossible to make it perfectly exact, I'll be glad to receive the best you can do.

• If you run through the debugger, or for some reason suddenly find yourself in the debugger, a traceback would be appreciated. For those who don't know how to do this, the command is SHOW CALLS. If you know what you're doing, I'd like you to go one step further, and SET MODULE the (say) top ten modules that are listed in the result of SHOW CALLS, so I can see the call sequence as closelly as possible.

• If you have a patch to fix the bug, please send it to me, with a short description of what it really fixes (I don't want to have to guess your intensions), even if it looks obvious to you.