Developer documentation: Difference between revisions
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
* Valgrind: Memory allocation/free checker. See [[Using Valgrind]] section for details on how to use it with Amanda. | * Valgrind: Memory allocation/free checker. See [[Using Valgrind]] section for details on how to use it with Amanda. | ||
: Valgrind is especially useful in debugging glibc errors. Error messages such as ''*** glibc detected *** ....'' are errors detected by glibc in Amanda memory allocation. Please report all such problems to the amanda-hackers mailing list or [http://forums.zmanda.com Amanda forums]. | |||
: You can workaround the glibc error detection by setting environment variable MALLOC_CHECK to 1. Please note that this might cause Amanda to fail later. | |||
== Static source code analysis == | == Static source code analysis == | ||
Revision as of 17:20, 8 August 2006
Code documentation
- Software architecture
- Secure API
- Virtual tape API
- Server/Client communication
- Application API
- Event API
- Driver-Taper protocol
- Reading amanda configuration
Developer tools
- Lint : lint makefile target is available for Amanda source tree. Run "make lint" to do static analysis of Amanda source code.
- Valgrind: Memory allocation/free checker. See Using Valgrind section for details on how to use it with Amanda.
- Valgrind is especially useful in debugging glibc errors. Error messages such as *** glibc detected *** .... are errors detected by glibc in Amanda memory allocation. Please report all such problems to the amanda-hackers mailing list or Amanda forums.
- You can workaround the glibc error detection by setting environment variable MALLOC_CHECK to 1. Please note that this might cause Amanda to fail later.
Static source code analysis
Coverity and Klocwork have been running their static analysis tools on the latest Amanda source code and making the results available for the Amanda developers to analyse and fix the defects. Currently (July 7, 2006), we have zero defects found by these tools. We are thankful to these companies for making these tools available and in general, helping to improve quality of open source projects.