** All communications should happen on dsdp-dd-dev mailing list for visibility.

** All communications should happen on dsdp-dd-dev mailing list for visibility.

−

** By next meeting: Lead should have requirements at minimum, but should also have protoype if at all possible, since having something to look at will generate better feedback.

+

** By next meeting: Lead should have requirements at minimum, but should also have prototype if at all possible, since having something to look at will generate better feedback.

* Current developer commitments (used to build table above)

* Current developer commitments (used to build table above)

** TI

** TI

Line 234:

Line 237:

*** Need to think about run-time memory map changes that are tied to the OS. Debugger will need to look at the MMU structure and also need to know about kernel data structures to handle the effective-to-physical address translation.

*** Need to think about run-time memory map changes that are tied to the OS. Debugger will need to look at the MMU structure and also need to know about kernel data structures to handle the effective-to-physical address translation.

CDT has requests to provide customized versions of variables and registers view. Probably will happen after CDT 3.2.

Using compatibility mode right now for flexibile hierarchy (for 3.1). Still need more investigation for how to expose customization.

TI:

We need flexible hierarchy exposed at CDI layer.

We use disassmebly view. Need a disassembly memory renderer.

Summary, they need flexibility at top and bottom.

They would like to see CDT define a more embedded-centric user experience without major changes to CDI.

Some view customizations.

Freescale:

Multi-core flexibility is important.

Nokia:

Similar comments to TI.

ATI

Builds against Eclipse platform, but haven't had a chance to look at 3.2 yet.

AMI

Builds against Eclipse platform.

Migrated an old VB debugger. Looked at CDT and did some prototyping, but decided it would be too much work.

They are lacking some features using the platform directly, but also believe they have less problems. One big issue was using GDB with their architecture.

First product: Oct 05 and based on 3.1.

Biggest issue is trying to use the memory view with their architecture.

Haven't prototyped against 3.2 EDM yet, but they can benefit from simplified hiearchy. Update policies are also critically important because of very slow target connections. Will focus on 3.2 after April.

Continually re-evaluate CDT. Could potentially use parts of CDT.

PalmSource

Have a released product on 3.0 with a customized CDT.

Working on a 3.1-based product with un-modified CDT. Trying to use GDB.

EDM 3.2 Progress Update – Darin W (IBM)

Moving forward, our API's are provisional, so we can still make changes.

March 30 - M6 feature freeze - only 3 weeks of development left

Columns and removing the last remaining synchronous interfaces

What's next after the 3.2 release?

How much feedback they get will determine how quickly these provisional API's can be public

Would need feedback in first 3 months: July - Sept

The customized view content may have to go through another cycle.

125374 - multi-column support in variables view: patch posted. Darin says this is close to the actual design. Ted would like more granuality in toggling specific columns on and off. Ted will add this to bug entry.

Plugable cell editors probably won't make the release. Ted to look at provided a patch to possibly help get this in.

API versioning - adding new interfaces on top of old ones vs. deprecating. When are interfaces collapsed together

Intention is that the adapters would live for a while in order to enable the backward-compatible debug model.

Using the editor with multiple debugging backends

Double-click gutter action - how is this resolved when the same editor is shared between two debug engines.

Seems to be a bigger problem that spans multiple projects: CDT, DD, PTP

Performance discussion

IBM will come to EclipseCon that shows performance across multiple versions

Leader drives discussions and prototyping on their technology. Leader initiates conference calls, starts a wiki page (see link above), collects requirements, and investigates/delegates prototyping. Leader is responsible for making sure the discussion is progressing. Leaders have commit rights to DD.

Team members help provide requirements and help prototype.

All communications should happen on dsdp-dd-dev mailing list for visibility.

By next meeting: Lead should have requirements at minimum, but should also have prototype if at all possible, since having something to look at will generate better feedback.

Current developer commitments (used to build table above)

TI

1 half-time engineer

Plan to update memory rendings, registers view, and variables view over the course of this year. Targeting Eclipse 3.1.2. right now management. Eclipse 3.2 product will release late summer / early fall.

WR

2 half-time+ engineers

Picking up 3.2 in fall release.

Freescale

Still working on first eclipse based product, so not yet ready to commit to providing fixes for any issues. After first release, they will have more breathing room for possible contributions.

PalmSource

Also releasing first product, but could probably get some resources approved if community can delegate some work, especially in CDT. Looking for direction and needs from Mikhail.

Really want to contribute, but have no resources yet. Could possibily contribute a debug console.

Nokia

Would like to contribute work on the views. Currently working on second Eclipse product. Looking at adding extensible breakpoint behavior and possibly some work on variable detail formatting for c++. After that they'll look at feedback from customers to help set priorities.

How can we get better participation to help Darin out on the debugger interfaces and views?

Where do we want to go next? Volunteers for implementation?

New breakpoint features?

More memory rendering?

Multi-core

Sample debugger implementation from Wind River?

Debug console

Committer List

This list is based on the sub-project leads who volunteer to build use-cases and coordinate prototyping for platform improvements. The commiters will have edit access to the Wiki and DSDP/DD CVS repository.

SPIRIT Discussion

Debug working group is probably needed to drive the SPIRIT definition.

Ideal if Eclipse could join the consortium. ARM and Mentor can be interfaces, too.

Hobson could work on setting up the debug working group. Hobson will also check on what they can make available for parsers. Hobson will check on licensing of SPIRIT XML files.

Next steps

Each member company to look into joining SPIRIT

DSDP-DD and DSDP-TM to nominate representative for a debug working group

DSDP-DD and/or DSDP-TM to build tools for generating/reading/validating SPIRIT files. AI for Aaron to talk to company about potential contributions. No Java Parser available yet for SPIRIT - we could contribute this in DD.

Doug - WR's data files standards

Two feature requests from SPIRIT

Board initialization specification

Help file indexing so registers can point to Silicon Vendor's pdf/html manuals

Mapping between debug format and registers - does this belong in SPIRIT or elsewhere?

Disassembly information should be a part of this - eventually we'd like table-driven disassembly - separate discussion

Endianness, default display size: byte, word, long, double, etc.

Help index

Long description for tool tip

Feedback on additional memory spec requirements

Flash - should be a separate discussion - CFI standard (?)

Cache

Virtual - should be a separate topic - ATI limited the XML to what's physically on the chip. - need to describe MMU structure

Need to think about run-time memory map changes that are tied to the OS. Debugger will need to look at the MMU structure and also need to know about kernel data structures to handle the effective-to-physical address translation.