20 likes | 140 Vues
This proposal, dated July 20, 2005, outlines the advantages and drawbacks of integrating GDB with Eclipse's Debug Interface. It discusses the need for separate processes, which may cause performance issues, and addresses challenges such as maintaining non-object-oriented C code. The document emphasizes the importance of modularity, robustness, and extensibility. It advocates for collaboration on reusable debug components while maintaining open-source principles. Key items include enhanced memory access, rich feature support for diverse object file formats, and potential for creating new projects under Eclipse’s framework.
E N D
GDB Advantages GDB Drawbacks Proposal Going Forward Eclipse Debug I/F • GPL • Proprietary source code must be maintained separately. • Forces GDB and Target Server to be separate processes causing performance degradation. • C – code non object oriented, harder to maintain. • Modularity • Synchronous API (especially for run) • Prevents memory reads and writes while target is running. • Already open source • Robust implementation • 1000’s of test cases written • Plenty of customer feedback • Feature rich • E.g., support for many different object file formats. • Collaborate on creating reusable debug components. • Open Source. • Using eclipse plug-in framework. • Can be combined to create a debug server • Eclipse Debug I/F • CDT I/F • Compiled Language I/F? • Seek additional supporters willing to contribute components • Which eclipse project? • Device Debugging. • CDT. • Create a new project. Compiled Language Support Program Loader Breakpoint Manager Call Stack Walker Dis-Assembler Symbol Table Expression Evaluation MI I/F CDT CDI I/F • Debug Server • Symbol table • expression evaluation, • c-stepping • breakpoint management • etc… Debug Server Source Stepping GDB • CDT changes? • More extensibility • i.e., GDB is extensible, CDT is not. Symbol File Reader Target Server