** Plan to do some prototyping against flexible hierarchy after 3.2 is released.

−

*** Plan to do some prototyping against flexible hierarchy after 3.2 is released.

+

* Mikhail Khodjaiants, QNX

−

** Mikhail Khodjaiants, QNX

+

** (presentation)

−

*** (presentation)

+

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

−

*** 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.

−

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

+

** TI:

−

*** TI:

+

*** We need flexible hierarchy exposed at CDI layer.

−

**** We need flexible hierarchy exposed at CDI layer.

+

*** We use disassmebly view. Need a disassembly memory renderer.

−

**** We use disassmebly view. Need a disassembly memory renderer.

+

*** Summary, they need flexibility at top and bottom.

−

**** 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.

−

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

+

*** Some view customizations.

−

**** Some view customizations.

+

** Freescale:

−

*** Freescale:

+

*** Multi-core flexibility is important.

−

**** Multi-core flexibility is important.

+

** Nokia:

−

*** Nokia:

+

*** Similar comments to TI.

−

**** Similar comments to TI.

+

* ATI

−

** ATI

+

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

−

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

+

* AMI

−

** AMI

+

** Builds against Eclipse platform.

−

*** Builds against Eclipse platform.

+

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

−

*** 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.

−

*** 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.

−

*** First product: Oct 05 and based on 3.1.

+

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

−

*** 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.

−

*** 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.

−

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

+

* PalmSource

−

** PalmSource

+

** Have a released product on 3.0 with a customized CDT.

−

*** 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.

−

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

*** Virtual tree - turned out to be more complicated than they thought.

+

* Stuff in M5 (public API freeze)

−

*** Virtual table

+

** Virtual tree - turned out to be more complicated than they thought.

−

*** Incremental load

+

** Virtual table

−

** Stuff not in M5

+

** Incremental load

−

*** Scopes / drag and drop

+

* Stuff not in M5

−

*** Columns

+

** Scopes / drag and drop

−

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

+

** Columns

−

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

+

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

−

*** Columns and removing the last remaining synchronous interfaces

+

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

−

** What's next after the 3.2 release?

+

** Columns and removing the last remaining synchronous interfaces

−

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

+

* What's next after the 3.2 release?

−

*** Would need feedback in first 3 months: July - Sept

+

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

−

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

+

** Would need feedback in first 3 months: July - Sept

−

** 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.

+

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

−

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

+

* 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.

−

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

+

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

−

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

+

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

−

** Using the editor with multiple debugging backends

+

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

−

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

Agenda & Attendee List

Presentations

Minutes

Eclipse 3.2 Debug Platform - Demos / feedback session on prototyping

The current state of the flexible hierachy aligns well with WR's debugger implementation.

Main issues at this point:

Need retargetable actions

Need public interface to get at standard images for label providers

Column support in views is incomplete at this point

Alan Boxall

Implemented directly against platform

Moving from 3.0 to 3.1 - the biggest challenge was to get the multi-threaded UI to talk to their synchronous debug engine.

They queue up all asynchronous requests. They use a lot of caching.

They are using the compatibility mode right now.

Taking advantage of 3.2 EDM in the future: eventually, IBM's debug engines will drive the hieararchy.

Number of jobs is somewhat alarming. (See performance discussions below.)

Plan to do some prototyping against flexible hierarchy after 3.2 is released.

Mikhail Khodjaiants, QNX

(presentation)

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

Update policy will have to be part of viewer, and model proxy will have to be part of the model.

Need to form a workgroup to address the issues in Samantha's presentation. Need to collect use cases from folks in this group.

Need to share a common look-and-feel, even if the implementation is in the model.

What's in 3.2

You can create model Proxies that tell how and when debug events are handled

Not there: a generic update policy

Memory View

Demo by Ted Williams (WR) of new renderer for memory view.

DD group would like this contributed

Other features

Programmatic foreground and background coloring

Customizable context menu

Symbol interleave with address bar

Optional confirm before write

Undo write

Column headings with sub-address - user can turn on and off

Contributions and Participation Discussion

See Felix's notes

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.

Paul Gingrich (TI)

Samantha Chan (IBM)

Ken Ryall (Nokia)

Kirk Beitz (Freescale)

Ewa Matejska (PalmSource)

Aaron Spear (Mentor)

Chris Recoskie (TI)

Darin Wright (IBM)

Pawel Piech (Wind River)

Pete Nichols (IBM)

Ewa Matejska (PalmSource)

Ted Williams (WR)

Miscellaneous

Eclipse 3.2 launching framework feedback

(subset of presentation from EclipseCon "Integrating Custom Debuggers into the Eclipse Platform")

Thursday TM/DD joint session notes

Doug: Update on DSDP, Plans for EclipseCon

See DSDP Website. Discussed new sub-projects: MTJ and NAB. Project pages will be posted in 1 to 2 weeks.

AI: Doug to setup lunch tables - due by Mar 1. Will coordinate with Doug S to not duplicate CDT areas.

BOF - schedule at the conference.

Hobston: SPIRIT

(2 presentations)

First presentation - SPIRIT for EDA - this is more for information

Second presentation - SPIRIT for Debuggers

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.