linuxpimp20

Im a beginner programmer and interested in how people go about debugging their programs? Do you have a favorite debugging program. Is there much debugging you can do without the help of third party tools? Any other thoughts or comments on debugging? thanks for ay replies in advance.

L7Sqr

I use gdb, but much less now.
I was turned on to a new tool called valgrind not to long ago.
Very powerful tool. (Linux specific)
I assume by your name the Linux issue will not be a problem.

Also, I dont think it falls under the heading 'debugging', but unit testing is a major help when working on a project. You can do your own unit testing or use third party software, either way your end product will benefit.

__________________
"...and though our kids are blessed their parents let them shoulder all the blame."
- The Quiet Things That No One Ever Knows [BrandNew]

linuxpimp20

yeah i've messed around with gdb a little bit but don't know much about debugging so i didn't know how to use it to it's full potential.

L7Sqr

It's nice to know your way around a debugger (gdb, for example), but it is better to not have to rely on one.
If you get teh basic functionality of a particular debugger down, stick with it. Each one has something appealing to someone (how's that for not saying much). But they will all do essentially the same thing.
There is google for when you really need to hack at it...

__________________
"...and though our kids are blessed their parents let them shoulder all the blame."
- The Quiet Things That No One Ever Knows [BrandNew]

linuxpimp20

i did open up kDbg and played with that a bit but read it is just a front end of gdb

DaWei

Generally speaking, the state of your machine at any given point is the result of its immediately preceding history. Information is key. It lives in your variables and it's reflected in the status provided by functions you use. Ignore these at your peril. A debugger is a history-recording and information-gathering device. Pick a good tool and learn to use it. You'll be more productive.

__________________
Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code.
Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers

Infinite Recursion

I use the compiler to catch my errors and gives me a line number, sometimes way off base, but it gives me a general idea. I haven't used a valid debugger since about 98, but I probably should pick up GDB or something... I agree with the production time being lost due to debugging.

__________________
http://jasonpowers.net

"There are a thousand hacking at the branches of evil to one who is striking at the root."

Polyphemus_

I always debug my code by hand... when something doesn't work, I first search where the error takes place, using this nice little macro:

and after that i just print all the values the wrong code refers to.