Making your debugging efforts count: best practices using the CDT Debugger
Developers spend a large part of their time debugging, with estimates putting that number above 50%. At the same time, applications continue to reach new levels of complexity and require better debugging solutions. In recent years, much work has been directed at improving the CDT Debugger to address those realities, yet many developers still rely on the most basic of debugging features. Even more, some developers continue to rely solely on printf-debugging.
In this talk, we will cover a series of best practices that will not only improve developer productivity but also help reach those still resisting the use of a full-featured debugger. We will describe or demo features such as:
- using dynamic-printf to avoid recompilation and deployment, thus avoiding the draw-backs of printf-debugging
- using reverse debugging to find bugs on the very first run
- making use of the upcoming, full-featured GDB console for quick and flexible control of the complete debug session
- using the Standalone Debugger for quick deployment and quick startup
- debugging an application running in a Docker container
- the upcoming ability to connect Eclipse/CDT to an already running GDB session
- and more
Join us and keep at the bleeding edge of C/C++ Application Debugging.