Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

CDT/Obsolete/MultiCoreDebugWorkingGroup/calls/minutes

< CDT‎ | Obsolete‎ | MultiCoreDebugWorkingGroup
Revision as of 07:00, 17 November 2010 by Unnamed Poltroon (Talk) (November 16, 2010)

Multi-Core Debugging Work Group Conference Calls

Conference call dates

Next call

November 30, 2010

Previous calls

November 16, 2010

Agenda for next call

Minutes of previous calls

November 16, 2010

Attendees:

  • Patrick Chuong (TI)
  • Dobrin Alexiev (TI)
  • Pawel Piech (WindRiver)
  • Doug Schaefer (WindRiver)
  • Pete (Tensilica)
  • Amen (Tensilica)
  • Norman Yi (Analog Devices)
  • Bill Swanson (Tilera)
  • John Cortell (Freescale)
  • Marc Khouzam (Ericsson)

Minutes:

  • Level of expected contributions from interested parties
    • Patrick and Dobrin have time allocated to this
    • Marc has time allocated for this
    • Pete can have someone help on UI work
    • Other commitments will clarify as the effort takes shape
  • Conference calls - is the proposed schedule satisfactory?
    • Seems as good as any other
  • High-level preliminary goals
  • Current state of affairs (including Patrick and Dobrin's nice work)
  • Way forward
  • Task definition and assignment
  • Pin and Clone status


==

TI's uses cases all focus on 10 to 50 contexts in the debug view. They currently feel that dealing with more than 100 contexts requires a new approach. TI's approach is to use the Debug View with a recursive set of containers, where the backend debugger remains the top-level entity.

From a user-perspective, we want to be able to actively focus on a small amount of contexts, while making the others available in case they become of interest.

Filtering of information is essential to this effort. Grouping and hiding are trying to address this.

Clean up wiki page to help people add their use-cases of interest, to help keep focus on the problems we face. [Marc]

Discussions on Tilera's Grid view:

    • The view has proven useful, but mostly when knowledge about the underlying hardware was relevant to the problem being debugged.
    • Tilera saw that software designers still view their software as a generic grouping of processes and threads, as shown in the Debug View.
    • Different users approach different problems in different ways. We should give users different views, etc, to tackle problems and let them choose what suits their needs.
    • Concerns were voiced about having two selection providers (Debug View and Grid view), but Bill confirmed he was able to get it to work. A demo will be given at the next call.
    • Someone asked if PTP had to deal with multiple selection providers for their views. We did not know the answer to this.

Dobrin described his efforts:

    • Use a recursive set of container context in DSF/DSF-GDB
    • Worked tracked in Bug 240280
    • Issues with Deltas when enabling recursive containers
    • Does anyone have a use-case where a container would also have a stack frame under it? Currently no, so we won't pursue this at this time.
    • Dobrin will demo his progress at the next conference call

Patrick is working on the Pin & Clone feature:

    • Pin & Clone effort
    • He has posted a small patch for platform which would allow other projects (e.g., CDT) to implement Pin and Clone. He is waiting for the platform team to review the patch in detail.
    • Patrick was ready to give a demo but we ran out of time. We will have the demo at the next conference call.
    • Worked tracked in Bug 327263. Anyone can try it out
      • checkout the platform org.eclipse.debug and org.eclipse.debug.ui plugins
      • apply the latest patch available in Bug 327263
      • import the test plugin also attached to Bug 327263
      • Start cloning and pinning views!
    • After the demo, we can start discussing and potentially bringing to the cdt-dev list the question of having this feature committed to CDT (pending the approval of the small platform patch)

Code Reviews would be valuable. With people actively working on this effort, we could code review each others work.

We will need to allocate time to do proper documentation for the features we will implement in this effort.

Back to the top