Debug/Phone 5-Nov-2009

Call Info

Meeting Title:	Conference Call on Device Debugging
Date & Time:	Thursday 3 Sep 2009 at 8:00am PDT / 10:00 am CDT / 11:00am EDT
USA/Canada tool free dial-in:	(866) 869-3090
International dial-ins:	Austria 01 92 87 547, Germany 06 92 22 21 61 10, Sweden 08 56 61 94 27, France 01 70 73 27 20, UK 02 08 11 81 026 or 08 44 57 90 592 (Complete list of international dial in numbers)
Passcode:	5107492128#

Attendees

• Wind River
  • Pawel
  • Randy
• IBM
  • Darin
  • Samantha
• Freescale
  • John Cortell
  • Daniel
• Ericsson
  • Marc K.
• Intel
  • Norbert Schulc
• ARM
  • Mikhail
• TI
  • Dobrin
• Nokia
  • Ken Ryall

Agenda and Minutes

• Status
  • Pawel
    • Flexible hierarchy bugs
    • Reviewing breakpoint improvements
  • Darin
    • Committed checkbox support in flex viewer
    • Split JDT tests
    • Design doc. for launch templates
    • Infrastructure for launch templates in core plugins
    • Support Ant-based external tool builders
    • Started UI for launch templates
  • Samantha
    • Reviewed mem view defects (and applied)
    • Started testing BP view
    • Reviewed launch template design
    • Samantha moving to another team (leaving IBM debug team, but a new person will join: "Jeremy Swan"), _Justin Calm_ will take over memory view maintenance work
• Breakpoint View Improvements
  • Review by Darin, Pawel
  • Need a default model proxy for IBreakpoint (to enable enablement/disablement)
  • Is it feature compatible
  • Need IP approval.
• ToggleBreakpointFactory questions (Marc)
  • Trying is a new kind of breakpoint: how will it affect other debuggers.
    • Other debuggers such as JDT will ignore it.
    • Other CDT debuggers will need to be updated to ignore the new breakpoint type.
• Breakpoint actions
  • (Marc) Can CDT breakpoint actions be executed by the back end?
  • (Ken) Actions can be executed back end, there's nothing in the framework preventing back end actions.
  • (Ken) Update: started refactoring CDT breakpoints, will try to get in for M4.
• Launch templates
  • Working on user interface for M4.
  • UI will stay relatively simple
  • Nesting of templates will not be allowed.
  • Scoping: will be too tricky for the initial implementation. If there's a default template for a project, LC's are not created based on a resource.