Download GCT User Manual
Transcript
User’s Manual 43 Bug Reports Appendix C: Reporting Bugs I can spend only a limited amount of time on unpaid GCT support. Please help me spend that time productively by making your bug reports as useful as possible. Check GCT Troubleshooting; you may find a solution to your problem. As a first resort, send bug reports to me ([email protected]) in preference to the mailing list. For a bug in the documentation, include the document version number and GCT version number (both of these are on the title page). For a software bug, please do the following: - Tell me what machine and version of UNIX you’re using. What argument was given to config.gcc? - Include a complete input file and control file. If possible, make the input file a preprocessed input file (by using ’gct -E source.c > FILE-TO-SEND.c’). This will reduce the chance that I won’t be able to reproduce the bug because it depends on the contents of system include files. - Rerun your example with that input file, and use ‘gct -v’ to cause GCT to print out its version number and a detailed log of what it did. - Describe what is wrong with GCT’s behavior (even if it’s obvious). - Include your email address in the body of the bug report. - Put your phone number in the bug report, in case return mail to you fails. More information, such as stack backtraces and so on, can wait. I’ll ask you for them if I need them.