| 1. |
-
Getting to Know gdb [Linux Journal]
- This article was adapted from the book Programming with GNU Software, published by O'Reilly & Associates.
URL: http://www2.linuxjournal.com/lj-issues/issue29/1298.html
|
| 2. |
-
gdb homepage [GNU project]
- The purpose of a debugger such as GDB is to allow you to see what is going on `inside' another program while it executes--or what another program was doing at the moment it crashed.
URL: http://www.gnu.org/software/gdb/gdb.html
|
| 3. |
-
gdb Manual Page
- man page for gdb.
URL: http://hegel.ittc.ukans.edu/topics/linux/man-pages/man1/gdb.1.html
|
| 4. |
-
List of C programming tools
- Synopsis from the book "Red Hat Unleashed". Mentions xxgdb, cproto, gdb, calls, indent, gprof, f2c, and p2c.
URL: http://sunsite.net.edu.cn/tutorials/linux/rhl27.htm#E67E27
|
| 5. |
-
Fixing Memory Leaks
- This document aims at programmers and testers wishing to hunt for memory leaks in theirs or other's
applications. A lot of testing and debugging has to invested to keep up with the stability of the underlying UNIX
operating systems so the following could be of some help.
After a few words on the theory it mainly concentrates on a simple tool that called LeakTracer to demonstrate
how to get going. I'll happily accept any kind of contribution that will help to correct and complete this paper.
URL: http://www.tu-harburg.de/~smhp2803/memoryleaks.html
|
