• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 320
  • Last Modified:

Fine tune my debugging skills.


I am wondering if there is a book anyone could recomend and/or link of how to use VC++6.0 and such debugger more efficiently. To learn more details.

I have my manuals that came with the compiler, but you know how manuals are. They tend to leave the layman in the dust.

I would like to seriously improve my debugging skills.

For example, to be able to debug apps that have hard time compiling under the debug version. To know why with much more detail.

A hard core debugging book/link for VC++6.0 and family (I will accept family if I can use info to relate).

A debugging for dummies with good details.

4 Solutions
Jaime OlivaresSoftware ArchitectCommented:
Personally I think that improve your debugging skills means to decrease your logic mind capabilities. I, and many others programmers don't use debuggers. When you code orderly, you will be able to detect and deduce where was every problem, without using debugging options, just some MessageBox() calls.
Better you can choose a 'Good Programming' book. Somethink like:
http://www.amazon.com/exec/obidos/tg/detail/-/0735619670/104-6575783-7307911 (Code Complete)
http://www.amazon.com/exec/obidos/tg/detail/-/0201563657/qid%3D1094353302/104-6575783-7307911 (C++ programming style)
http://www.amazon.com/exec/obidos/tg/detail/-/0201760428/qid%3D1094353302/104-6575783-7307911 (Exceptional C++ style)

Good luck,
There are a lot of places to go for debugging techniques and information.

One of my favorite books on the subject is "Debugging Applications" by John Robbins.

Microsoft's over for debugging -- "Debugging Tools for Windows - Overview" is at:


Your debugging ability is developed with practice. Experience is a very important part of the process of improving one's debugging skills -- the more you do it the better you will get at it. Use your debugger to help you understand what is going on "under the hood", even down to the assembly level.
Debugging is more bout knowing how to analyse and look for errors than bout learning bout a particular debbugger whether VC++ debugger or GDB ..if you are good atdebuggging , you can just pick up any debugger pretty fast .. its just a matter of syntax /command /optiosn after that

a good link is : http://www.robelle.com/library/smugbook/todebug.html


also learn what is the assert() function , they are also helpful at times in pinpointing locations where yuo are asuming some vakues and actually it is not so etc etc
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

You could try avoiding having to debug, by coding defensively.

When you write each statement, think about what could go wrong: subscripts out of range, API returns an error code, NULL pointer, passing value instead of address, string overflow, and arithmetic overflow are the biggies.   Add if(0 statements to check pointers and API results.  

That will prevent 88% of debugger-type errors.

Jaime OlivaresSoftware ArchitectCommented:
I agree with grg99, that's what I am talking of. As programming teacher, I recommend my students to improve good programming better than good debugging. Actually I am a bad debugger, but solve my problems rapidly without it.
RJSoftAuthor Commented:
Well, I decided to get

Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers
by Everett N. McKay

(after reading and re-reading reviews and amazon details)

True, Robbins seems to be the leading author in the debugging arena. But I am not at that level. I use to use the debugger that came with Borland C++ so I know simple things of how to step etc. But after I switched to VC I got lazy and started using MessageBox to display values. Partly cause VC makes simple debugging more of a pain than Borland's old compilers did.

Of course using MessageBox works in a crude kind of a way, but I sense that it has seriously weakened my abilities. I would feel much more confident knowing how to use VC's debugger more efficiently. Perhaps save serious time.

The main book of Robbins (non NT) is also out of print. Or has been replaced with an NT/Windows version. The older Robbins book is the one that really interest me as it goes into great detail of debugging even to the level of building your own debugger. Also how to interpret those assembler core dumps. But, like allot of other things program related I go off chasing rabbits and forget my main objectives.

The older Robbins book is also costly $99. I fear that it's way above my level. Surprizingly the newer release with NT I can purchase for about $4 used. I probably will purchase that for the heck of it.

So I am settling for a more straight forward to the point book with tips and tricks. Which to me practical is gold. Im not trying to conquor the universe, just have some insight on how to debug properly.


RJSoftAuthor Commented:

Although we dis-agree on the use of a debugger, I felt I should give you some points for
the link to "Code complete". A good book I will have to look into.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now