Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

DSDP/DD/Disassembly Phone 10-January-2008

< DSDP‎ | DD

Call Info

Meeting Title: Conference Call on Device Debugging
Date & Time: Thursday 10 January 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, Mikhail, Randy, Ken Ryal

Agenda and Notes

  • Comments on proposals: Special viewer for both components and Disassembly window management
  • Disassembly window managment
    • Mikhail: can implement abstract class that helps implements ISouceDisplay with:
      • source lookup.
      • "no source available" page with message to show disassembly when there is no source code
    • Mikhail: theoretically it's possible to open disassembly editor that is provided by the specific model, this will require adding an extension point
  • Special viewer
    • Three elements:
      • Disassembly Context - There are separate disassembly editors for different disassembly contexts, where the disassembly context could be a core, process, address space, etc.
      • Base - Current "base" depends on the selected debug context (stack frame, etc). Current base address can be changed in an editor.
      • Line - either source or disassembly line or symbol information, etc. Viewer requests lines, then it requrests label for each line. Viewer also requrests annotations for each line.
    • Model also provides an event proxy to notify the viewer that the content has changed. This even proxy can notify the viewer when IP or breakpoint annotations have changed. Also it can notify the viewer when memory has changed.
    • Retargetable actions (breakpoints, run to line)
      • Viewer finds the line at which the retargetable action is called. Then it finds the retargetable target for the selected line.
      • Currently the IToggleBreakpointTarget is registered with the whole disassembly editor, which then retargets the action to user's toggle breakpoin target (new interface).
      • Pawel: I would like to make this framework re-use the toggle breakpoint target infrastructure from platform, and avoid creating new interfaces.
    • Syntax coloring is still a missing feature.
    • Presentation context may not be appropriate for disassembly, or it may need to extend the existing presentation context interface.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.