Differences between version 8 and predecessor to the previous major change of CommonProgrammingBugs.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 8 | Last edited on Thursday, February 5, 2004 3:00:13 pm | by JohnMcPherson | Revert |
| Older page: | version 7 | Last edited on Monday, September 15, 2003 9:28:01 am | by SamJansen | Revert |
@@ -24,15 +24,6 @@
bt full will take the __b__ack __t__race of the core file and if you specify "full" it'll show you all the variables along the way.
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]
-* electric fence
-* [MMGR] (works well with C++)
-* [mcheck] (part of libc6
-dev)
-* [MALLOC_CHECK_] environment variable
-* [LD_DEBUG] environment variable
-* [DMALLOC|http://www.dmalloc.com]
-* 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
-* AddToMe: any other neat tools you know of?
+----
+See our DeBugging page for more details.
