[ < ] | [ > ] |  | [ << ] | [ Up ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 1.9 Feedback and Bug Reporting

If you find a bug in Crystal Space there are two ways to report it to the developers. The preferred method of reporting bugs is to use the SourceForge support request mechanism that can be found at:

https://sourceforge.net/tracker/?group_id=649&atid=100649

To use the SourceForge trackers, you must have a SourceForge user id, and be logged in.

Additionally, you can send a message to the main Crystal Space mailing list (see section Mailing Lists) at crystal-main@lists.sourceforge.net.

Try to give as much information as possible about the bug, including:

- Crystal Space version number. If it is a CVS snapshot then include the time that you downloaded it. If you are using CVS directly then state when it was that you last did an update.
- Operating System (Windows (95, 98/SE/ME, NT4, 2000, XP), MacOS/X, Unix -- GNU/Linux, FreeBSD, etc. -- ...).
- The compiler that you used (GCC, Mingw, MSVC, ...).
- Architecture (Intel x86, AMD x86, AMD 64, SPARC, MIPS, M68K, Alpha, PowerPC, ...).
- Graphics adapter (brand/model, total on-board memory, driver version, ...).
- Video settings (color depth, resolution, Crystal Space video driver, ...).
- Description of the problem.
- Exact error message (or output of Crystal Space). If possible it would be nice to get the output of the Crystal Space application with ``-verbose'` commandline option. If you are using a gcc based compiler and you compiled in optimize mode then you'll also need to add the ``-console'` option. If you compiled with MSVC and you build in release mode then you'll need the ``-noconsole'` option.
- How to reproduce the crash (if it is reproducible).
- A fix for the bug if available (Unified diff files are desirable).

[ < ] | [ > ] |  | [ << ] | [ Up ] | [ >> ]

This document was generated using texi2html 1.76.