Closed thknx closed 4 years ago
I doubt that running the dashboard inside vscose is a viable setup. The dashboard needs a proper TTY and apparently vscode is not providing one.
I doubt that running the dashboard inside vscose is a viable setup. The dashboard needs a proper TTY and apparently vscode is not providing one.
Then why gdb-dashboard works on MacOS with same vscode =)
Different implementations of the "DebugConsole"? I don't know, I'm not a vscode user myself, let me try to reproduce this...
By the way, I use C/C++ Extension (by Microsoft) with below configuration: I have .gdbinit in my folder which does remote debug session. So when I press vscode-debug button it automaticly connects to remote gdb session (I mean without manually run gdb from terminal inside vscode)
# launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": "C++ Launch",
"type": "cppdbg",
"request": "launch",
"program": "${workspaceFolder}/kernel",
"stopAtEntry": false,
"cwd": "${workspaceFolder}/",
"linux": {
"MIMode": "gdb"
},
"symbolLoadInfo": {
"loadAll": true,
},
}
]
}
In any case even without that error the GDB terminal you end up with runs the GDB/MI interface meaning that you cannot just type commands (you need to use the -exec <command>
syntax) plus you won't have the tab-completion. Last but not least (at least in my case) ANSI codes doesn't work...
The fix should avoid that error but I repeat that IMHO what you're trying to do is not a reasonable setup.
gdb-dashboard works with standart terminals, but when I run it in vscode IDE, DebugConsole gives me there errors:
(Not: I tried on XOrg, I am using Debian10)