cdt-gdb-adapter
cdt-gdb-adapter copied to clipboard
CDT GDB Debug Adapter
**Problem** During a regular debug session with the CDT GDB adapter, I see the following error notification a lot:  This is for example provoked when hovering over comments, keywords,...
**Problem** One cannot use the Debug Console to execute GDB commands while a CPU/thread is running. You get an error message about no `frameId` being available. This includes CLI commands...
**Problem** Providing faulty input to a GDB server can cause it to terminate * after the GDB server was at first successfully spawned... * but before GDB tries to attempt...
**Problem** GDB/MI comes with a set of asynchronous breakpoint notifications. These announce changes to breakpoints. Currently, the CDT GDB adapter does not process and translate them into DAP breakpoint events....
**Problem** It is common for embedded debugger IDEs to have a reset button. Such reset buttons often have configurable and/or device specific reset strategies. Normally, the device ends up at...
I found a phenomenon similar to [cortex-debug issue]( https://github.com/Marus/cortex-debug/issues/923) ``` #include #include void function_one() { int num = 10; printf("function one\r\n"); } void function_two() { int num = 20; printf("function...
You often don't get an obvious enough visual feedback that a debug session is launching. Especially if you are new to VS Code, it's easy to miss the debug control...
See the discussion when breakpoint modes got added in https://github.com/eclipse-cdt-cloud/cdt-gdb-adapter/pull/350#issuecomment-2636935359 - it seems that for Windows host debugging (at least on GitHub actions) that hardware breakpoints are not functioning correctly.
During the debug session, when user navigates and opens the `Disassembly View` in the VSCode, the Disassembly View focuses on an incorrect line when it is compared program counter (pc)...