Debugging is the process of removing bugs.
Tools for detecting memory management and threading bugs are, among others, valgrind (Linux) and DrMemory (Windows).
The process of improving the runtime speed is called profiling.
- The key question in debugging is: How would I know if the program actually worked correctly? [1]
- When defining a template, first design and debug a non-template version; later generalize by adding parameters [2]
- Making the data members of a class private and the member functions of the class public facilitates debugging [3]
For profiling tools,see profiling.
- Bjarne Stroustrup. Programming. 2009. ISBN: 978-0-321-54372-1. Chapter 5.9: 'The key question in debugging is 'How would I know if the program actually worked correctly?'
- Bjarne Stroustrup. The C++ Programming Language (4th edition). 2013. ISBN: 978-0-321-56384-2. Chapter 23.8, page 698: '[4] When defining a template, first design and debug a non-template version; later generalize by adding parameters'
- Paul Deitel, Harvey Deitel. C++11 for programmers (2nd edition). 2014. ISBN: 978-0-13-343985-4. Chapter 3.4, Error Prevention Tip 3.1. page 47: 'Making the data members of a class private and the member functions of the class public facilitates debugging because problems with data manipulations are localized to either the class's member functions or the friends of the class'