Next: 7.2 Requesting Features
Up: 7. Support
Previous: 7. Support
Contents
Index
7.1 Reporting Bugs
The recommended way of reporting bugs is using the infrastructure
of the sourceforge site. You can follow the status of bug reports
there and have an overview about the known bugs.
Bug reports are automatically forwarded to the developer mailing list
and will be fixed ASAP. When reporting a bug, it is very useful to
include a small test program (the smaller the better) which reproduces
the problem. If you can isolate the problem by looking at the generated
assembly code, this can be very helpful. Compiling your program with
the --dumpall option can sometimes be useful
in locating optimization problems. When reporting a bug please maker
sure you:
- Attach the code you are compiling with SDCC.
- Specify the exact command you use to run SDCC, or attach your Makefile.
- Specify the SDCC version (type "sdcc -v"),
your platform, and operating system.
- Provide an exact copy of any error message or incorrect output.
- Put something meaningful in the subject of your message.
Please attempt to include these 5 important parts, as applicable,
in all requests for support or when reporting any problems or bugs
with SDCC. Though this will make your message lengthy, it will greatly
improve your chance that SDCC users and developers will be able to
help you. Some SDCC developers are frustrated by bug reports without
code provided that they can use to reproduce and ultimately fix the
problem, so please be sure to provide sample code if you are reporting
a bug!
Please have a short check that you are using a recent version of SDCC
and the bug is not yet known. This is the link for reporting bugs:
http://sourceforge.net/tracker/?group_id=599&atid=100599.
Next: 7.2 Requesting Features
Up: 7. Support
Previous: 7. Support
Contents
Index
2008-03-04