Hi,
How to debug a c++ program in c++. I want the command. Suppose my program is prime.cpp. I am not getting any errors. How to debug it.

This might be a good place to start:

http://www.unknownroad.com/rtfm/gdbtut/gdbtoc.html

(FYI, the author, Richard M. Stallman, is one of the "founding fathers" of the Open Source movement)

With so little information about the problem, I'm not sure if the previous suggestion was the right one for your case. In simpler debugging cases a scattering of diagnostic print statements can be more appropriate.

Obviously, you have to use your skill and judgement to figure out where to put the print statements and what you want to print out, but you didn't want me to put you out of a job, did you?

And, if you are doing this to learn, you might be wanting to try every approach available to you, just for grins.

Hi, palisetty_suman -

Yours was a fair question, and I tried to give you a fair answer.

If you're using an IDE to program C++ (for example, KDevelop or Eclipse on Linux, or Visual Studio on Windows), then you probably first want to learn more about your IDE's debugger.

If you're planning on programming C++ on Linux, then you'll almost certainly be using GCC (either directly, from a command line, or behind a GUI IDE). In this case, the command-line "GDB" is definitely a worthwhile tool to learn.

The *last* thing you want to do is rely on "printf" statements. Using them is inevitable. But there are usually better, more effective ways to debug. The trick is to expose yourself to the higher-level tools available (like GDB or Visual Studio), then fall back on "printf" only when you need to.

Good luck - and have fun!

IMHO .. PSM

Thanks paul boss. But sorry to say that I haven't got the answer. I am using c++ on linux and i just want a command to debug a program.
like
command filename. I just want the command to debug a filename for errors and execution. Thanks.

I gave you a command in the first post: I also gave you a tutorial about how to use "gdb". More importantly, the tutorial is also about debugging strategies and tips in general.

If you are expecting a command that you can run that will automagically remove bugs from an incorrectly written bit of code, then you are setting your expectations rather high.

In addition, maybe you should look at static analysis http://en.wikipedia.org/wiki/List_of..._code_analysis which may be closer to what you want. But you will still have work to do; the best that you can expect is that something will point out potential trouble areas and you will have to come up with a way of writing correct code that corresponds to your intentions.

My assumption is that your program is probably a fairly simple one, of the type that you might be set as a learning problem in the early stages of a programming course.