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.
It is my belief that the error message is actually coming from this module in VS CODE, but truthfully I'm not sure
it is a very tangled web of modules and sorting this stuff out is non-trivial.
Meanwhile, I'll copy some stuff from the other ticket:
Compile host and VSCODE host is a Linux server in another room.
Remote JTAG server is my laptop running OpenOCD.
Target is: Microsemi Polarfire RISCV soft cpu core.
All of this works standalone out side of VS CODE.
I know that process (GDB_REMOTE) well - I use Emacs GUD Mode like this all the time.
I also use a tool known as "GDBGUI" - it works well to, see: https://www.gdbgui.com/
In the end, the "Trace' feature - gives this log message when it dies (the entire trace is in the other ticket)
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (135) DebuggerPid=1669\n"},"seq":38}
1: (135) DebuggerPid=1669
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (150) <-1001-gdb-set mi-async on\n"},"seq":40}
1: (150) <-1001-gdb-set mi-async on
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (153) ->1001^done\n"},"seq":42}
1: (153) ->1001^done
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (153) ->(gdb)\n"},"seq":44}
1: (153) ->(gdb)
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (154) 1001: elapsed time 5\n"},"seq":46}
1: (154) 1001: elapsed time 5
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (165) Send Event AD7MessageEvent\n"},"seq":48}
1: (165) Send Event AD7MessageEvent
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (168) <--gdb-exit\n"},"seq":50}
1: (168) <--gdb-exit
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (169) <-logout\n"},"seq":52}
1: (169) <-logout
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (169) ->^exit\n"},"seq":54}
1: (169) ->^exit
--> E (output): {"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/Launch","data":{"VS.Diagnostics.Debugger.ImplementationName":"Microsoft.MIDebugEngine","VS.Diagnostics.Debugger.EngineVersion":"17.4.30208.2","VS.Diagnostics.Debugger.HostVersion":"17.4.30208.2","VS.Diagnostics.Debugger.AdapterId":"cppdbg","VS.Diagnostics.Debugger.Launch.ErrorCode":1005,"VS.Diagnostics.Debugger.Launch.IsError":true}},"seq":56}
--> R (launch-2): {"type":"response","request_seq":2,"success":false,"command":"launch","message":"Unable to start debugging. Specified argument was out of the range of valid values. (Parameter 'arch')","body":{"error":{"id":1005,"format":"Unable to start debugging. Specified argument was out of the range of valid values. (Parameter 'arch')"}},"seq":58}
I'm trying to "CROSS POST" this bug from :
But do not know how to do so.
https://github.com/microsoft/vscode-cpptools/issues/11051
It is my belief that the error message is actually coming from this module in VS CODE, but truthfully I'm not sure it is a very tangled web of modules and sorting this stuff out is non-trivial.
Meanwhile, I'll copy some stuff from the other ticket:
Compile host and VSCODE host is a Linux server in another room. Remote JTAG server is my laptop running OpenOCD. Target is: Microsemi Polarfire RISCV soft cpu core.
All of this works standalone out side of VS CODE. I know that process (GDB_REMOTE) well - I use Emacs GUD Mode like this all the time. I also use a tool known as "GDBGUI" - it works well to, see: https://www.gdbgui.com/
In the end, the "Trace' feature - gives this log message when it dies (the entire trace is in the other ticket)
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (135) DebuggerPid=1669\n"},"seq":38} 1: (135) DebuggerPid=1669 --> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (150) <-1001-gdb-set mi-async on\n"},"seq":40} 1: (150) <-1001-gdb-set mi-async on --> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (153) ->1001^done\n"},"seq":42} 1: (153) ->1001^done --> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (153) ->(gdb)\n"},"seq":44} 1: (153) ->(gdb) --> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (154) 1001: elapsed time 5\n"},"seq":46} 1: (154) 1001: elapsed time 5 --> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (165) Send Event AD7MessageEvent\n"},"seq":48} 1: (165) Send Event AD7MessageEvent --> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (168) <--gdb-exit\n"},"seq":50} 1: (168) <--gdb-exit --> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (169) <-logout\n"},"seq":52} 1: (169) <-logout --> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (169) ->^exit\n"},"seq":54} 1: (169) ->^exit --> E (output): {"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/Launch","data":{"VS.Diagnostics.Debugger.ImplementationName":"Microsoft.MIDebugEngine","VS.Diagnostics.Debugger.EngineVersion":"17.4.30208.2","VS.Diagnostics.Debugger.HostVersion":"17.4.30208.2","VS.Diagnostics.Debugger.AdapterId":"cppdbg","VS.Diagnostics.Debugger.Launch.ErrorCode":1005,"VS.Diagnostics.Debugger.Launch.IsError":true}},"seq":56} --> R (launch-2): {"type":"response","request_seq":2,"success":false,"command":"launch","message":"Unable to start debugging. Specified argument was out of the range of valid values. (Parameter 'arch')","body":{"error":{"id":1005,"format":"Unable to start debugging. Specified argument was out of the range of valid values. (Parameter 'arch')"}},"seq":58}