Skip to main content

Skip over site navigation to main content

developerWorks  >   Open source  >   Technical library  >  

Technical library view  RSS for Open source

 developerWorks
 Related links:    Redbooks

Filter your search and/or enter a keyword. If you don't filter your search or enter a keyword, the search results will default to all results.

 
 
 
  1 - 2 of 2 results    Hide Summaries
Title   Type   Date  

Table that contains the results that meet the search criteria.

Interfacing with the CDT debugger, Part 1: Understand the C/C++ debugger interface
The Eclipse C/C++ Development Tooling (CDT) is one of the most well-known open source environments for C/C++ development, and its full-featured debugger plays a large role in its popularity. What isn't as well known is that the CDT framework can be extended to support custom debuggers. With the right plug-in, a custom debugger can access the full spectrum of the CDT's graphical debugging environment: code-stepping, watchpoints, breakpoints, register contents, memory contents, and variable views. Learn how to construct this plug-in, with a focus on the C/C++ Debugging Interface (CDI). 		Articles 10 Jun 2008  
 
Interfacing with the CDT debugger, Part 2: Accessing gdb with the Eclipse CDT and MI
The graphical debugging environment provided by the Eclipse C/C++ Development Tooling (CDT) is about as good as it gets, displaying breakpoints, watchpoints, variables, registers, disassembly, signals, and memory contents. You can add new capabilities to this environment or access these views to display output from a custom debugger. But first, you need to understand the C/C++ Debugger Interface (CDI) and how it communicates with Eclipse. Part 1 describes the CDI at a high level, and this article presents a practical example: How the CDT uses the CDI and the Machine Interface (MI) to interface the GNU Debugger. 		Articles 24 Jun 2008  
 
  1 - 2 of 2 results    Hide Summaries
Not finding what you're looking for? Suggest Content