Teach Yourself Borland C++ in 14 Days - portal

Quiz
Using the Debugger
1. How do you set a breakpoint on a particular line of code?
2. What is an invalid breakpoint?
3. How do you set a conditional breakpoint?
4. How can you change the properties of an item in the Watch List?
5. What’s the quickest way to add a variable to the Watch List?
6. What tool do you use to view the data members and methods of a class?
7. How do you trace into a function call when stepping with the debugger?
8. How can you change the value of a variable at runtime?
9. What is the difference between the TRACE and WARN macros?
10. How do you view the output from the TRACE and WARN macros?
Exercises
1. Load the ScratchPad program that you created a few days ago. Place breakpoints in
the FileOpenClick() and FileSaveClick() functions. Run the program. When
program execution pauses, inspect the OpenDialog and SaveDialog classes, respectively.
2. Continuing with exercise 1, step through the program when you stop at a
breakpoint and examine the program’s operation as you step through the functions.
3. Load the DebugTst program you created earlier in this chapter. Place a breakpoint
in the WatchBtnClick() function. Add the s and x variables to the Watch List. Add
each variable to the Watch List four times. Edit each of the watches and change the
display options. Run the program and step through the function to see the effects
in the Watch List.
4. Add a conditional breakpoint to the function in exercise 3. Place it on the line
immediately after the line that reads int x = Width. Make the condition x == 0
and run the program. What happens?
5. Continuing with exercise 4, edit the breakpoint and change the condition to
x > 400. Run the program. Change the window’s size and click the Watch Test
button. Repeat this process several times, changing the window’s size each time.
What happens?
6. Load any program and switch to the Code Editor. Place the cursor on any line of
code and choose the Run to Cursor item from the Code Editor speed menu.
Experiment with the program until the breakpoint is hit.
425
11