Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Multi-core Working Group

I would like to join  this group. We at Tensilica have product based on CDT and very much interested in  multicore debugging feature .
Tensilica Technologies India Pvt Ltd
Pune , India

From: Marc Khouzam <marc.khouzam@xxxxxxxxxxxx>
To: "CDT DEV (cdt-dev@xxxxxxxxxxx)" <cdt-dev@xxxxxxxxxxx>
Sent: Mon, 4 October, 2010 7:55:41 AM
Subject: [cdt-dev] Multi-core Working Group


at the CDT Summit there was a lot of interest around bringing Multi-Core Debugging to the CDT.
I use the wording "Multi-Core" to denote a multi-node debugging session, where multiple
cores, multiple boards, multiple targets, etc, can be debugged.

We got an impressive demo from TI (Dobrin and Patrick) about the work they have been doing in
that field.  They showed a working implementation of the following features:
  - Grouping of debug-view elements
  - Debug operations (step, resume) on groups
  - Hiding of debug-view element types
  - User-selectable debug-view layouts
  - Debug-view hierarchy configuration in the launch
  - Pin and Clone of debugger views

Many summit participants expressed their interest in seeing such features be part of the CDT,
and were open in helping make Multi-Core Debugging a reality for CDT (you know who you are :-)).
To make this happen, I suggest the following:

- forming a Multi-core Debugging working group
- holding regular conference calls to discuss division of tasks, progress, issues, etc
- dividing the effort into manageable, self-contained features
- establish clear targets for the next CDT release
- get commitments from interested parties on the work they can contribute

To make this effort public, I have added a "Working Groups" section to the bottom of the
CDT wiki, where people can follow and contribute to this work.  We'll use this page for
conference-call details, minutes-of-meetings, and other relevant information.

This first email is meant to get the ball rolling and hopefully get different people/companies
to discuss internally how much they will be able/willing to contribute, and what their goals
are.  This work is an effort to take CDT Debugging to a new level, but also an opportunity
for companies that already provide Multi-Core debugging to have their say in the direction
the open-source community will take.

I personally will be absent for the month of October so I haven't planned a first conference
call.  If people want to get started before November, please go ahead.  If not, I'll schedule
something for the second week of November.

Comments and suggestions on this approach are very welcomed.

Take care.

cdt-dev mailing list

Back to the top