Changes between Version 9 and Version 10 of Debugging
- Timestamp:
- 01/12/13 17:49:23 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Debugging
v9 v10 91 91 == Venerable Print Statements == 92 92 When all else fails, or just when appropriate, sprinkling some {{{print}}} statements around the critical sections of code is often the best way to get a clearer picture of what is really going on.. 93 94 95 == Memory Leaks == 96 97 === In C code === 98 If the memory leak is one of the Cython parts or in a C library, use regular tools, like [http://blog.devork.be/2008/12/finding-memory-leaks-in-python.html valgrind]. 99 100 === In python code === 101 Needs documenting, [http://mg.pov.lt/objgraph/ objgraph] is a good place to start. 102 103