Able to use a graphics debugger to debug program is crucial in programming. It could save you countless of hours guessing on what went wrong. Step 1: Set an Initial Breakpoint - A breakpoint suspends program execution for you to examine the internal states e. Before starting the debugger, you need to set at least one breakpoint to suspend the execution inside the program.
Set a breakpoint at main function by double-clicking on the left-margin of the line containing main. A blue circle appears in the left-margin indicating a breakpoint is set at that line. The program begins execution but suspends its operation at the breakpoint, i. As illustrated in the following diagram, the highlighted line also pointed to by a blue arrow indicates the statement to be executed in the next step.
At each of the step, examine the value of the variables in the "Variable" panel and the outputs produced by your program in the "Console" Panel , if any. You can also place your cursor at any variable to inspect the content of the variable. Single-stepping thru the program and watching the values of internal variables and the outputs produced is the ultimate mean in debugging programs - because it is exactly how the computer runs your program! Step 4: Breakpoint, Run-To-Line, Resume and Terminate - As mentioned, a breakpoint suspends program execution and let you examine the internal states of the program.
To set a breakpoint on a particular statement, double-click the left-margin of that line or select "Toggle Breakpoint" from "Run" menu. You could set a breakpoint at the statement immediately outside the loop e.
Alternatively, you can place the cursor on a particular statement, and issue "Run-To-Line" from the "Run" menu to continue execution up to the line. Always terminate your current debugging session using "Terminate" or "Resume" till the end of the program. I can's stress more that mastering the use of debugger is crucial in programming.
Explore the features provided by the debuggers. Modify the Value of a Variable: You can modify the value of a variable by entering a new value in the "Variable" panel.
This is handy for temporarily modifying the behavior of a program, without changing the source code. Step-Into and Step-Return: To debug a function , you need to use "Step-Into" to step into the first statement of the method.
You could use "Step-Return" to return back to the caller, anywhere within the method. Alternatively, you could set a breakpoint inside a method. Eclipse 4. You should see a new instance of eclipse - with the latest version of eclipse CDT plugins. Select "Eclipse Application" and click New. This appears to be a more widely used launching technique. Until you are familiar with the CDT code base, using a Debug Launcher and experimenting with breakpoints is probably the best way to get a warm fuzzy feeling if you have doubts about modifications you are making.
If you wish to contribute your changes to CDT see these instructions. If you want just patch up your local installation you can export plugin s to which source patch is applied:. You can use the Eclipse installer Oomph to setup the Eclipse installation and everything required to get started with CDT development.
The initial setup can take a while. You should see some information in the status bar which you can click on arrows for details. Some errors may occur after Eclipse launches and the Eclipse Updater starts. After the initial setup, you should have a complete Eclipse environment to work on CDT. In January the git repos for numerous CDT and related code was merged into a single git repo. See Bug When working on master branch after January nothing special needs to be done.
However if you are working with the launchbar or tools. The old git repos will eventually be removed as their history has fully migrated to the main org. Back to the top.
0コメント