Differences between version 4 and predecessor to the previous major change of CommonProgrammingBugs.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Saturday, August 23, 2003 5:46:12 pm | by SamJansen | Revert |
| Older page: | version 3 | Last edited on Friday, June 13, 2003 9:07:49 pm | by JohnMcPherson | Revert |
@@ -25,13 +25,13 @@
The first line should be the place where your bug occured. If you look at this line you'll probably find you're doing something silly (like addressing past the end of an array, or using a pointer that has been free()'d).
Other neat tools for diagnosing memory errors are:
-* valgrind
+* [Valgrind]
* electric fence
-* mmgr
(works well with C++)
+* [MMGR]
(works well with C++)
* [mcheck] (part of libc6-dev)
* [MALLOC_CHECK_] environment variable
* [LD_DEBUG] environment variable
* printf(3)
* catchsegv (prints the backtrace of a program that segfaults) - don't forget to compile with "-g" if you want file names and line numbers
* <add a neat tool you know of here>
