Jump to: navigation, search

Difference between revisions of "DSDP/DD/Phone-2-October-2008"

< DSDP‎ | DD
m (New page: == Call Info == {|border=1 cellspacing=0 cellpadding=4 | Meeting Title: | '''Conference Call on Device Debugging''' |- | Date & Time: | Thursday 6 March 2008 at 7:30am PDT / 10:30am EDT ...)
 
m
 
Line 19: Line 19:
  
 
== Attendess ==
 
== Attendess ==
 +
* Pawel Piech, Randy Rohrbach, Ted Williams, (Wind River)
 +
* Darin Wright, Pete Nichols, Samanta Chan (IBM),
 +
* Marc Khouzam, Dominique (Ericsson)
  
 
== Agenda and Notes ==
 
== Agenda and Notes ==
 
* ''Status bu sub-group''
 
* ''Status bu sub-group''
** ''SPIRIT (Anthony)''  
+
** ''SPIRIT (Anthony)''
 
** ''Memory (Samantha)''
 
** ''Memory (Samantha)''
 +
*** Ted posted a proposal for simplifying the workflow
 +
*** Plan: go to address bar - waiting for updated patch which ties into rendering
 +
*** Plan: remove
 
** ''Disassembly (Mikhail)''
 
** ''Disassembly (Mikhail)''
 
** ''DSF (Pawel)''  
 
** ''DSF (Pawel)''  
 +
*** Keepign APIs backward compatible.
 +
*** Adding UI imrovments in views: stepping synchronized with view updates
 
** ''GDB/MI (Pawel)''
 
** ''GDB/MI (Pawel)''
 +
*** Support for latest GDB
 
** ''Multi Context (Pawel)''
 
** ''Multi Context (Pawel)''
 +
*** Working on prototype for debug-view less debugging.
 
* ''Discussion Topics''
 
* ''Discussion Topics''
 
** Merging with CDT
 
** Merging with CDT
 +
*** Time: after 1.1
 +
*** Separate components for DSF, and DSF-GDB
 +
** CDI-GDB features not in DSF-GDB
 +
*** Created a list of bugs with [cdi] in subject which identify features which are missing from DSF-GDB
 +
*** We're asking the community to vote on features which are most important to them.
 +
** Memory: Ted's proposal
 +
*** Removal of memory monitors pane
 +
**** Enable the memory view layout to be configurable based on active debug context. 
 +
**** Investigate how to de-couple the rendering view pane from the selected memory monitor.
 +
**** Investigate how to hide the split pane mode.
 +
*** Go to address bar
 +
**** Ted to post an update patch.
 +
*** Update modes:
 +
**** Memory blocks are shared between memory views, which makes it difficult to have different update modes.
 +
** Traditional memory rendering
 +
*** Need to create a patch to evaluate it in context of debug platform.

Latest revision as of 10:32, 2 October 2008

Call Info

Meeting Title: Conference Call on Device Debugging
Date & Time: Thursday 6 March 2008 at 7:30am PDT / 10:30am EDT
USA tool free dial-in: (888) 545-8370
International dial-in: (770) 659-3936
Passcode: 5107492128#

Attendess

  • Pawel Piech, Randy Rohrbach, Ted Williams, (Wind River)
  • Darin Wright, Pete Nichols, Samanta Chan (IBM),
  • Marc Khouzam, Dominique (Ericsson)

Agenda and Notes

  • Status bu sub-group
    • SPIRIT (Anthony)
    • Memory (Samantha)
      • Ted posted a proposal for simplifying the workflow
      • Plan: go to address bar - waiting for updated patch which ties into rendering
      • Plan: remove
    • Disassembly (Mikhail)
    • DSF (Pawel)
      • Keepign APIs backward compatible.
      • Adding UI imrovments in views: stepping synchronized with view updates
    • GDB/MI (Pawel)
      • Support for latest GDB
    • Multi Context (Pawel)
      • Working on prototype for debug-view less debugging.
  • Discussion Topics
    • Merging with CDT
      • Time: after 1.1
      • Separate components for DSF, and DSF-GDB
    • CDI-GDB features not in DSF-GDB
      • Created a list of bugs with [cdi] in subject which identify features which are missing from DSF-GDB
      • We're asking the community to vote on features which are most important to them.
    • Memory: Ted's proposal
      • Removal of memory monitors pane
        • Enable the memory view layout to be configurable based on active debug context.
        • Investigate how to de-couple the rendering view pane from the selected memory monitor.
        • Investigate how to hide the split pane mode.
      • Go to address bar
        • Ted to post an update patch.
      • Update modes:
        • Memory blocks are shared between memory views, which makes it difficult to have different update modes.
    • Traditional memory rendering
      • Need to create a patch to evaluate it in context of debug platform.