The article explains Linux debugging tools and techniques in various scenarios. It reviews debugging problems, including segmentation faults, memory overruns and leaks, and hangs. This article also appears in the August 2002 issue of the IBM developerWorks journal.
If you haven’t been there yet, IBM developerWorks is a truly great site. It has tons of tutorials and papers on things like Regular Processing, Ruby, GNU/Linux, and XML.
I was surprised to look through this article and see absolutely no mention of Valgrind (see http://developer.kde.org/~sewardj/), which is perhaps the best dynamic memory debugging utility ever made. Instead there was only coverage of older utilities such as Electric Fence.
Do somebody know a good visual frontend for GDB?
Do somebody know a good visual frontend for GDB?
There’s DDD (see http://www.gnu.org/software/ddd/), but ultimately you’ll be better off using gdb from the command line.