You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Due to ArduPilot's highly custom simulation bringup (sim_vehicle.py), and lack of use of CMake or other common build tool, it's difficult to use VSCode's GUI support for configuring, building, testing, and debugging.
Merge one of the dev's launch.json and tasks.json files that works on master, and then allow others to start contributing. When working, this provides the ability to use a keyboard shortcut to configure, build, run sim_vehicle.py, attach gdb, and inspect the code at a breakpoint WITHOUT using gdb's CLI. This can be faster and easier, but it still allows console-commands for gdb.
Here is a hard-coded launch and task showing a breakpoint being triggered in SITL.
And, ideally when you launch sim_vehicle from command line, you could add a --vscode-debug option that would launch the vscode debugger inside the current VSCode session microsoft/vscode#10979
Feature request
Is your feature request related to a problem? Please describe.
Due to ArduPilot's highly custom simulation bringup (sim_vehicle.py), and lack of use of CMake or other common build tool, it's difficult to use VSCode's GUI support for configuring, building, testing, and debugging.
Developers are maintaining their own custom configs, but these aren't shared.
Describe the solution you'd like
Merge one of the dev's
launch.json
andtasks.json
files that works onmaster
, and then allow others to start contributing. When working, this provides the ability to use a keyboard shortcut to configure, build, runsim_vehicle.py
, attachgdb
, and inspect the code at a breakpoint WITHOUT usinggdb's
CLI. This can be faster and easier, but it still allows console-commands for gdb.Here is a hard-coded launch and task showing a breakpoint being triggered in SITL.
Describe alternatives you've considered
ArduPilot/ardupilot_vscode_devenv#1
See the following branches:
And the current wiki: https://ardupilot.org/dev/docs/debugging-with-gdb-using-vscode.html?highlight=vscode
Which has this flaw of needing to pick the process:
https://stackoverflow.com/questions/65723608/vs-code-debugging-is-it-possible-to-supply-process-id-pgrep-x-myprog-for
And, GDB console needs
exec
prefixed all the time:microsoft/vscode-cpptools#106
And, ideally when you launch sim_vehicle from command line, you could add a
--vscode-debug
option that would launch the vscode debugger inside the current VSCode sessionmicrosoft/vscode#10979
Some discussion in discord can be found here: https://discord.com/channels/674039678562861068/674039678982422579/1137475852838387913
Platform
[x ] All
[ ] AntennaTracker
[ ] Copter
[ ] Plane
[ ] Rover
[ ] Submarine
The text was updated successfully, but these errors were encountered: