Jan Jurzitza

have you maybe tried changing the `"valuesFormatting"` setting in the launch config? Depending on your programming language and GDB version different values will display in differing qualities.

the watch list variables are currently implemented without any variable rendering

remote host? If you want to attach remotely you need to either debug over SSH (running lldb-mi on the remote system with debug binary and sources available on the remote...

try setting ``` "printCalls": true, "showDevDebugOutput": true ``` in your debug configuration for it to show logs of what it's doing

with that error output I would just assume you are compiling without debug information. Also I think you might need to give your task a proper id/name, I don't know...

https://sourceware.org/gdb/onlinedocs/gdb/Signaling.html#Signaling try `signal SIGINT` in the debugging console

with printCalls and showDevDebugOutput you already enabled maximum logging. Try maybe setting `magomipath` to `"C:\\Program Files (x86)\\VisualD\\mago-mi.exe"` Otherwise I would try the C/C++ extension instead for debugging D code.

hm hard to tell what the issue might be here, I would guess on the LLDB implementation having a bug here because this looks like the LLDB output log.

I haven't tried it a lot but basic functionality should work with it. On windows I would recommend using the other debugging extension (C/C++ Extension) instead

try changing the debug engine to `gdb` and the `gdbpath` to the path to your server executable if you want to use a custom gdb mi server. The protocol changes...