cdt-gdb-vscode
cdt-gdb-vscode copied to clipboard
CDT GDB Visual Studio Code Extension
When using openGdbConsole=true now working in v2.0.3, the console is actually opened but the user is prompted to confirm the pagination mode (I think): "--Type for more, q to quit,...
I've got a question regarding the statement in the repo's README.MD: We begin with the statement: "This is a Visual Studio Code extension that supports debugging using gdb and any...
The following error is reported via an alert window when starting a remote debug session in a Docker container. Given the error, it probably doesn't matter, but I was attempting...
Hi, I think that the Debug Session should be closed after the gdbserver or gdb exits. I've also killed the gdb, but the Debug Session will still be there ...
Removed avoidable VS Code references. See discussion on original PR #138 .
The extension is freezing when I step over a fflush. example: ``` C #include int main(void) { printf("hello\n"); fflush(stdout); // works fine printf("world"); fflush(stdout); // frezes return 0; } ```...
## Environment * CDT GDB Debug Adapter Extension: version 2.4.1 * VSCodium version: 1.105.17075 * Launch configuration ```JSON { "name": "run", "type": "gdb", "request": "launch", "program": "test", "arguments": "TSAN_OPTIONS=second_deadlock_stack=1", "cwd":...
We have a couple of new features that should be better documented: - Use of data breakpoints: through watch window and command - Auxiliary GDB connection: needs bit more explanation...
currently everything in the debugger console seems to be handled as an expression to evaluate - but that's already possible using the watch pane in the debugger; other extensions therefore...
### ENV **host**: ```shell os: windows10 gdb: 10.2 cdt-gdb-vscode: v2.0.5 ``` **target**: ```shell arch: arm32 gdbserver: 7.6 ``` I am currently using cdt-gdb-vscode for remote debugging in VS Code. Here...