Re: Advanced c++ debugging techniques on Unix
- From: Bernhard Agthe <Bernhard.Agthe@xxxxxxxxxxxxxxx>
- Date: Tue, 31 Oct 2006 08:34:34 +0100
Hi,
I imagine there likely to exist some "must read" too for the second.
So, here I am polling for those of you that have been impressed by
books, tools or libs on advanced c++ debugging techniques on Unix.
It looks like debugging is some kind of "black art" ;-) There is not much on that topic in general.
For me it works best to first resolve all compiler errors and warnings (gcc/g++ is very informative ;-) and then to test the program extensively. Segmentation faults are relatively easy to debug (using gdb or valgrind), logical faults require lots of printf/cout.
But mostly debugging depends on program design - I write my programs so that errors will lead to an immediate chrash (segmentation fault) and get my program so safe that this doesn't occur ;-) Also using several small modules instead of few large ones helps if you can identify by the nature of the error which module is concerned...
Doing step-by-step debugging seems not very efficient for me - a professor at university said about it "you debug the CPU, not your program."
Those books that reveals "what, how and why using this tool/lib (open
source or commercial) when faced with this kind of problems". Or books
that teach "You did it wrong, man! Here is how to do this."
Go ahead, set up a wiki invite some people in this group and you'll be able to produce some "Debugging C and C++ Howto"...
Ciao...
.
- References:
- Advanced c++ debugging techniques on Unix
- From: Maitre Bart
- Advanced c++ debugging techniques on Unix
- Prev by Date: Re: In which case write() will be blocked
- Next by Date: Re: In which case write() will be blocked
- Previous by thread: Re: Advanced c++ debugging techniques on Unix
- Next by thread: suppressions in valgrind - to see leaks only
- Index(es):
Relevant Pages
|
|