home *** CD-ROM | disk | FTP | other *** search
- Error Reporting Form for the MAEstro Multimedia Authoring Environment
-
- If you find errors or would like enhancements to be made to any of the
- software in the MAEstro environment, please use this form to report
- errors or suggestions. It will help us more quickly track down the
- error.
-
- This error report form also covers the User's Guide. If some part of
- the User's Guide does not make sense to you, please report that as an
- error so we can rewrite the User's Guide to make things more clear.
-
- If you don't want to follow the form exactly, that's fine. It is just
- a suggested way to report errors; we have tried to include all the
- pertinent information we need to fix errors here.
-
- Please mail the following form, with your information, to
-
- maestro@sioux.stanford.edu
-
- -------------------------- Begin Here --------------------------
- 1. Which software is causing the problem?
- (e.g., DisplayTool, the Port Manager, vcrEdit, File Browser,
- User's Guide, etc.)
-
- Your Answer Here
-
- 2. What type of problem is it, briefly?
- (e.g., software doesn't compile, software crashes at run-time, I
- don't understand how to use your software with my applications,
- the User's Guide doesn't make sense somewhere, I can't print the
- User's Guide, etc.)
-
- Your Answer Here
-
- 3. Please describe the problem in as much detail as you can.
- The more information you can provide, the better chance we'll have
- of fixing the problem.
-
- Start Describing Here; Take As Much Space As You Need
-
- 4. Is the problem consistently reproducible? If so, how can we
- reproduce the problem? Are there any data files you could send to
- help us reproduce the problem?
-
- Include Explanation (And Relevant Files) Here
-
- 5. Can you include a transcript of the problem?
- * If the problem is a compilation problem, please include the
- output of "make", so we can see exactly what line(s) are
- causing the problem.
- * If the problem is at run-time, a stack trace would be of great
- help. Run gdb, CenterLine CodeCenter, or dbx on the core file
- dumped by the applications that crashed, and send the stack trace
- and all the values of currently known variables, if possible.
- You can't send too much debugger information. If you don't know
- how to produce a stack trace, please send mail to
- maestro@sioux.stanford.edu and we'll be happy to help you produce one.
- It might be helpful to rerun the application with a non-stripped
- version of the software, so the debugger can better tell us where
- the problem happened. By default, the MAEstro applications are
- installed stripped to decrease size; you might re-install not
- stripped; the master Makefile tells you how.
-
- 6. Do you know what caused the problem? If so, that would save us
- time trying to track down the cause if you already know.
-
- Your Answer Here
-
- 7. Do you have a fix for the error? If so, please include any
- relevant code, instructions, etc. Keep in mind that they will
- become property of Stanford University (we have to say that; please
- excuse us).
-
- Include Explanation And Relevant Information Here
-
- 8. Do you have suggestions for improvements?
-
- Your Answer Here; Take As Much Space As You Need
-
- 9. Any other comments or information you would like to add?
-
- Your Answer Here; Take As Much Space As You Need
-
-
-