1. Proposed Debugger Features Ken Ryall Warren Paul

2. Desired Debugger Features Debugging of project-less executables Enhanced Variable Formatting C++ runtime type inspection Enhanced breakpoints (actions, templates etc.) Support for address spaces Memory window enhancements Display variable addresses or containing register in Variables view Selectable scope for Variables view Multiple thread debug context Change the Program Counter Auto-update Views Cached-source for debugging Line table tick marks

3. Desired Debugger Features Display variable addresses or containing register in Variables view Selectable scope for Variables view Multiple thread debug context Change the Program Counter Auto-update Views Cached-source for debugging Line table tick marks Debugging of project-less executables Enhanced Variable Formatting C++ runtime type inspection Enhanced breakpoints (actions, templates etc.) Support for address spaces Memory window enhancements

4. Debugging Executables built outside of Eclipse When no project exists, only an executable Debugging without a project possible, but lots of existing code likes having a project Create a CDT project to facilitate debugging  Provides desired experience and leverages other features

5. C++ Executable Importer New Wizard imports C++ Executables

6. C++ Executable Importer Select one or more executables

7. C++ Executable Importer Create a new project or add to an existing one Create a pre- configured launch configuration

8. C++ Executable Importer Binary parsers extended to provide list of source files Browse sources and set breakpoints

9. C++ Executable Importer Issues Finding missing source files while browsing Finding missing source files while debugging Auto mapping common paths within different locations:  C:\mysource\BigProject\src\main.cpp  E:\cvs_proj\Projects\BigProject\src\main.cpp

10. Enhanced Breakpoints Breakpoint Templates – managing the creation of complex breakpoints Breakpoint Actions – extending what happens when a breakpoint is hit Saving and sharing breakpoints Naming breakpoints

11. Breakpoint Actions Controlling what happens when your breakpoint is hit Standard action is to stop in the debugger and update all the views Actions defined globally for a workspace One or more actions can be attached as properties of a breakpoint

12. Defining Breakpoint Actions Select from a list of available actions An extension point defines actions and manages their behavior <extension point="com.nokia.cdt.debug.breakpoints.breakpointBehavior"> <behaviorType name="Sound Action" class="com.nokia.cdt.debug.breakpoints.behaviors.Sound" id="com.nokia.cdt.debug.breakpoints.behaviors.Sound">

13. Applying Breakpoint Actions Set from breakpoint properties page One or more actions can be attached to a breakpoint Control the order of execution for each action

14. Some Breakpoint Actions Sound Action – play a specified sound Log Action – log a specified string or expression to the console Pause Action – update the debugger views, then continue Skip Action – move the PC past the breakpoint location, then continue Script Action – execute a script

15. Breakpoint Templates Assist in the creation of complex breakpoints Templates consist of properties only Apply to new or existing breakpoints Create templates from existing breakpoints Templates are named and are managed in their own list

16. Desired Debugger Features Debugging of project-less executables Enhanced Variable Formatting C++ runtime type inspection Enhanced breakpoints (actions, templates etc.) Support for address spaces Memory window enhancements Display variable addresses or containing register in Variables view Selectable scope for Variables view Multiple thread debug context Change the Program Counter Auto-update Views Cached-source for debugging Line table tick marks