Visual C++ 6 Unleashed

By MICKEY WILLIAMS and David Bennett

• Table of Contents
  • Copyright
  • About the Authors
  • About the Contributors
  • Acknowledgments
  • Tell Us What You Think!
  • Introduction
  • How to Use This Book
  • What You Need to Use This Book
  • What's New in Visual C++ 6.0
  • Contacting the Main Author
  • Part I: Introduction
  • Chapter 1. The Visual C++ 6.0 Environment
    • Developer Studio
    • The Project Workspace
    • The Workspace Window
    • Project Configurations
    • Converting Older Projects
    • Working with Multiple Projects
    • Working with Resources
    • Editing Resources
    • MFC AppWizard
    • ClassWizard
    • Component Gallery
    • Integrated Debugger
    • Command-Line Tools
    • Other Tools
    • Summary
  • Part II: MFC Programming
  • Chapter 2. MFC Class Library Overview
  • Chapter 3. MFC Message Handling Mechanism
  • Chapter 4. The Document View Architecture
  • Chapter 5. Creating and Using Dialog Boxes
  • Chapter 6. Working with Device Contexts and GDI Objects
  • Chapter 7. Creating and Using Property Sheets
  • Chapter 8. Working with the File System
  • Chapter 9. Using Serialization with File and Archive Objects
  • Part III: Internet Programming with MFC
  • Chapter 10. MFC and the Internet Server API (ISAPI)
  • Chapter 11. The WinInet API
  • Chapter 12. MFC HTML Support
  • Part IV: Advanced Programming Topics
  • Chapter 13. Using the Standard C++ Library
  • Chapter 14. Error Detection and Exception Handling Techniques
  • Chapter 15. Debugging and Profiling Strategies
  • Chapter 16. Multithreading
  • Chapter 17. Using Scripting and Other Tools to Automate the Visual C++ IDE
  • Part V: Database Programming
  • Chapter 18. Creating Custom AppWizards
  • Chapter 19. Database Overview
  • Chapter 20. ODBC Programming
  • Chapter 21. MFC Database Classes
  • Chapter 22. Using OLE DB
  • Chapter 23. Programming with ADO
  • Part VI: MFC Support for COM and ActiveX
  • Chapter 24. Overview of COM and Active Technologies
  • Chapter 25. Active Documents
  • Chapter 26. Active Containers
  • Chapter 27. Active Servers
  • Chapter 28. ActiveX Controls
  • Part VII: Using the Active Template Library
  • Chapter 29. ATL Architecture
  • Chapter 30. Creating COM Objects Using ATL
  • Chapter 31. Creating ActiveX Controls Using ATL
  • Chapter 32. Using ATL to Create MTS and COM+ Components
  • Part VIII: Finishing Touches
  • Chapter 33. Adding Windows Help
  • Part IX: Appendix

Integrated Debugger

Developer Studio includes a full-featured debugger for fixing those problems that inevitably manage to slip in. A good reference for the debugger is the online help, and we don't have the space to include it all here, so I will just mention a few things that you may find useful. More information about debugging can be found in Chapter 15, "Debugging and Profiling Strategies."

Looking at Your Data

When you are debugging, you will be concerned with the values represented by the variables in your program. The simplest way to do this in Developer Studio is to point the mouse at the variable in the source code and wait a second or two. A small tip box will appear that displays the current value of the variable.

For a more detailed view, you can use the right mouse button to produce a Context menu, which allows you to open a quick watch window for the selected variable. The quick watch window allows you to enter any expression you want to evaluate in the expression window. However, preprocessor constants (including resource ID constants) are generally not available for evaluation. To add this expression to the more permanent watch window, click the Add Watch button.

Debugging After Exceptions

At some time or another, you will almost definitely find yourself with an application that will trip over an unhandled exception. This will bring up a dialog box that will allow you to exit altogether or debug the application. You may actually load the debugger to view the current state of your application at the time of the exception, source code and all, even if you were not running your application from Developer Studio at the time!

Share This