List of Figures

Chapter 1: Bugs – Where They Come From and How You Solve Them

Figure 1-1: The debugging process

Chapter 2: Getting Started Debugging

Figure 2-1: Generating debugging information for a C# project

Figure 2-2: Generating debugging information for a Visual Basic .NET project

Figure 2-3: Setting the C++ compiler to generate debugging information

Figure 2-4: Turning off incremental linking in the C++ linker

Figure 2-5: C++ linker debug node settings

Figure 2-6: C++ optimization linker settings

Figure 2-7: The Visual Studio .NET debugger Modules window with a relocated DLL

Figure 2-8: Process Explorer showing relocated DLLs

Figure 2-9: Setting the base address for a DLL

Figure 2-10: The Environment Variables dialog box

Figure 2-11: An example of the symbol server database

Chapter 3: Debugging During Coding

Figure 3-1: The DefaultTraceListener message box

Figure 3-2: An ASP.NET application displaying an assertion using AssertControl

Figure 3-3: Example of a folded SUPERASSERT dialog box

Figure 3-4: Example of an unfolded SUPERASSERT dialog box

Figure 3-5: The Global SUPERASSERT Options dialog box

Chapter 4: Operating System Debugging Support and How Win32 Debuggers Work

Figure 4-1: The DBGCHOOSER configuration dialog box

Figure 4-2: The DBGCHOOSER debugger chooser dialog box

Figure 4-3: WDBG in action

Figure 4-4: An example symbol expansion

Chapter 5: Advanced Debugger Usage with Visual Studio .NET

Figure 5-1: Breakpoint dialog box about to set a quick breakpoint on a function

Figure 5-2: The Choose Breakpoints dialog box

Figure 5-3: Child breakpoints in the Breakpoints window

Figure 5-4: Breakpoint on any call to Console.WriteLine

Figure 5-5: The Find combo box

Figure 5-6: An example of remaining hit count breakpoint expressions

Chapter 6: Advanced .NET Debugging with Visual Studio .NET

Figure 6-1: Visual Studio .NET indicating that it can't set a breakpoint

Figure 6-2: Desperately seeking autoexpand help

Figure 6-3: The joy of autoexpands

Figure 6-4: The ecstasy of autoexpands

Figure 6-5: Turning on mixed mode debugging in a C# project

Figure 6-6: Turning on mixed mode debugging in a Visual Basic .NET project

Figure 6-7: Turning off property evaluation

Figure 6-8: Installing just the remote debugging portion of Visual Studio .NET

Figure 6-9: Main ILDASM display

Figure 6-10: MSIL for a method

Chapter 7: Advanced Native Code Techniques with Visual Studio .NET

Figure 7-1: Data breakpoint about to cause single stepping

Figure 7-2: Setting a data breakpoint

Figure 7-3: Hitting a data breakpoint

Figure 7-4: Autoexpand in a data tip

Figure 7-5: EEAddIns at work

Figure 7-6: A project set up for Pipe debugging

Figure 7-7: Exceptions dialog box

Figure 7-8: First chance exception dialog box

Figure 7-9: General.purpose register layout

Figure 7-10: The Visual Studio .NET Registers window

Figure 7-11: Stack before the AccessLocalsAndParamsExample function prolog

Figure 7-12: Stack during and after execution of the AccessLocalsAndParamsExample function prolog

Figure 7-13: The stack displayed in the Visual Studio .NET debugger Memory window

Chapter 8: Advanced Native Code Techniques with WinDBG

Figure 8-1: SDK installation selected during the Debugging Tools for Windows installation

Figure 8-2: The WinDBG Open Executable dialog box

Figure 8-3: The Processes And Threads window

Figure 8-4: Getting ready to do noninvasive debugging

Figure 8-5: The Event Filters dialog box

Figure 8-6: Filter Command dialog box

Chapter 9: Extending the Visual Studio .NET IDE

Figure 9-1: Macro Explorer window

Figure 9-2: Command window's IntelliSense popup executing a macro

Figure 9-3: Setting the /doc command.line option to produce an XML documentation comment file

Figure 9-4: Setting the Exceptions dialog box to stop on all exceptions

Figure 9-5: SettingsMaster Options property page

Chapter 10: Managed Exception Monitoring

Figure 10-1: Setting the system environment variables

Chapter 12: Finding Source and Line Information with Just a Crash Address

Figure 12-1: Standard Windows XP crash dialog box

Figure 12-2: Error Report Contents dialog box in Windows XP

Figure 12-3: The MAP file settings in the project Property Pages dialog box

Figure 12-4: The CrashFinder user interface

Chapter 13: Crash Handlers

Figure 13-1: Diagram of a crash handler

Figure 13-2: CrashTest dialog box

Chapter 14: Debugging Windows Services and DLLs That Load into Services

Figure 14-1: The Attach Debugging property page

Figure 14-2: DLL view for Process Explorer showing new DLLs added to the Notepad process

Chapter 16: Automated Testing

Figure 16-1: Script recording options for Tester

Figure 16-2: Keystroke recording start, tab key, and check break state machines

Figure 16-3: Keystroke recording normal key state machine

Figure 16-4: Keystroke recording Alt+Tab state machine

Figure 16-5: Mouse recording normal state machine

Figure 16-6: Mouse recording double click state machine

Chapter 17: The Debug C Run-Time Library and Memory Management

Figure 17-1: GFLAGS.EXE with settings for HEAPER.EXE

Figure 17-2: PageHeap allocation

Figure 17-3: Visual Studio .NET Debug toolbar after properly configuring the AppVerifier add.in

Figure 17-4: The AppVerifier add.in Options dialog box inside Visual Studio .NET

Figure 17-5: AppVerifier Test Settings dialog box

Figure 17-6: The /RTCs error report

Figure 17-7: Setting the /RTCx switches

Chapter 18: FastTrace: A High-Performance Tracing Tool for Server Applications

Figure 18-1: The common server tracing system

Chapter 19: Smoothing the Working Set

Figure 19-1: Model nonoptimized system

Figure 19-2: Model optimized system

Figure 19-3: Task Manager showing handles and GDI objects

Figure 19-4: Initiating a new configuration from the Configuration Manager dialog box

Figure 19-5: Creating a new Release.SWS configuration

Figure 19-6: Specifying the /ORDER file to a release build

Appendix A: Reading Dr. Watson Logs

Figure A-1: Dr. Watson UI

Figure A-2: Dr. Watson Log File View dialog box for Windows XP