Jan Jurzitza
Jan Jurzitza
oh but you might be right about the (...) embedded command syntax
The documentation in general is code-debugs job but having some standard documentation to base the code on would be really useful and would make debuggers more intuitive
Gonna reopen for further improvements
given that this extension is general purpose and not bound to one language we can't really provide a word definition provider. Registering one would basically mean we want it explicitly...
I meant to say this should not really be part of the debugger, but rather of the language extensions you download from vscode. Like the extensions that provide auto complete...
try playing around with the `valuesFormatting` property. Otherwise GDB probably doesn't give me the details to show anything better through the GDB MI API. "prettyPrinters" should however already be the...
the extension renders pretty printed values like GDB passes it to it, it does not implement language specific stuff or dereferences memory etc.
hm the commands not starting with a `-` should be run through `interpreter-exec` because that makes it feel more like a GDB console, good for people who are used to...
feel free to replace calls to sendRaw with sendCommand if they come from the extension and using `-interpreter-exec` User input to the debug console should still support GDB commands if...
I don't think the fix for this has been released yet, but it should be there on master.