|RE: [cdt-dev] Summit Agenda|
It extents org.eclipse.cdt.debug.core.CDebugger extension point and implements the ICDI* interfaces.
Its implementation talks to our DebugServer.dll – a COM dll that gets loaded in the Eclipse process space.
What do you call that?
I was thinking I am using standard terms J I guess I am not.
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mikhail Khodjaiants
Could you please clarify what did you mean by "non GDB CDI debugger". Is it GDB & CDI or GDB | CDI ?:)
Behalf Of Alexiev, Dobrin
Can you add to the conference list three more people from Texas Instrument?
We recently hooked up our debugger engine as a non GDB CDI debugger.
Along with that we did bunch of usability enhancements to CDT and Eclipse.
I was wandering if the community would be interested to see a demo of these enhancements.
If so, I can do a demo at the conference and discuss what we did to put these in the product.
Here are some of the enhancements:
Launch and debugger:
- Low level debugging – no projects and/or program required.
- Support for dynamic symbols – adding and removing of symbols.
- Debug Active Project – hiding the launch concept for beginners.
- Losing and recovering the connection to the debug target in the middle of a debug session.
- Enhanced breakpoint support – hardware breakpoints, symbolic breakpoints – giving more control to the back end debugger.
- Requesting the list of global variables from the debugger instead of the program file.
- Disassembly View – viewing the whole memory range, not only the current function.
- Showing virtual vs physical memory in the memory view
- Adding new breakpoints from a combo box in the Breakpoint View
- Selecting a start address form a combo box in both Memory and Disassembly View
- Added a drop down in the _expression_, Registers and Variables views for modifying of enums.
- Modifying values in the _expression_ View
- GUI testing infrastructure
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
I have done a little work on the agenda and have updated the wiki. You can see it at: http://wiki.eclipse.org/index.php/CDT/summitfall2006.
One thing of note is that the agenda proper ends at noon on Thursday. I have slotted Thursday afternoon as a “code clinic” where we can bring the discussions right down to the code level. People are free to stay and follow along but it will get pretty dry pretty quick. So if you want to catch an afternoon flight out on Thursday, you won’t miss too much J.
Also, I have slotted time at the beginning for each organization to introduce itself. I think it would help a lot of we understand more about ourselves, what we do with the CDT, and help finalize the agenda.
As always, please let me know if you have anything to add/change/remove.
QNX Software Systems
Eclipse CDT Project Lead
-- The 2006 ARM Developers' Conference, October 3-5, Santa Clara, US
Join ARM and its technology and tools Partners from around the world at the only industry event for developers of ARM Powered(R) solutions.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.