The Visual Studio MI Debug Engine ("MIEngine") provides an open-source Visual Studio Debugger extension that works with MI-enabled debuggers such as gdb and lldb.
MIT License
817
stars
217
forks
source link
`stopAtEntry` and `launchCompleteCommand` ignored for GDB remote targets #1014
MIEngine will ignore configuration parameters when connecting to a GDB server (either a literal gdbserver instance, or something else that implements that interface, like openocd). The default behaviour (stopAtEntry: true and launchCompleteCommand: exec-continue) is used regardless of user configuration.
This presents a major roadblock for using MIEngine-based tools (VSCode C/C++) for remote debugging, such as for embedded targets.
MIEngine will ignore configuration parameters when connecting to a GDB server (either a literal
gdbserver
instance, or something else that implements that interface, likeopenocd
). The default behaviour (stopAtEntry: true and launchCompleteCommand: exec-continue) is used regardless of user configuration.This presents a major roadblock for using MIEngine-based tools (VSCode C/C++) for remote debugging, such as for embedded targets.
References:
883
https://github.com/microsoft/vscode-cpptools/issues/3739 https://github.com/microsoft/vscode-cpptools/issues/2715 https://github.com/microsoft/vscode-cpptools/issues/978 https://github.com/microsoft/vscode-cpptools/issues/321#issuecomment-278635202