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
Question.
This issue tracker is not the place for questions. If you want to ask how to do something,
or to understand why something isn't working the way you expect it to,
use Community Forums or Premium Support
PlatformIO IDE.
All issues related to PlatformIO IDE should be reported to the PlatformIO IDE for VSCode repository
Development Platform or Board.
All issues (building, uploading, adding new boards, etc.) related to PlatformIO development platforms
should be reported to appropriate repository related to your hardware https://github.com/topics/platformio-platform
Feature Request.
Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose to keep the project small.
PlatformIO Core.
If you’ve found a bug, please provide an information below.
You can erase any parts of this template not applicable to your Issue.
Configuration
Operating system: Arch Linux
PlatformIO Version (platformio --version): PlatformIO Core, version 6.1.14
nvim-dap supports the capability to load launch.json configurations in neovim as follows:
-- Load VS Code launch configurations.ifvim.fn.filereadable(".vscode/launch.json") thenrequire("dap.ext.vscode").load_launchjs(nil, { ["platformio-debug"] = { "c", "cpp", "asm" } })
end
This makes it possible to benefit from the efforts put into VS Code's debugger integration. However, when I try to execute the launch config PIO Debug, nvim tells me that it does not have the platformio-debug adapter specified. I tried scouring a few repos on PlatformIO GitHub but could not find any mention about this adapter.
I expected that correctly specifying the platformio-debug adapter would allow the debugger integration in PlatformIO as well. Here's how it looks, if you're wondering.
What kind of issue is this?
Question.
This issue tracker is not the place for questions. If you want to ask how to do something,
or to understand why something isn't working the way you expect it to,
use Community Forums or Premium Support
PlatformIO IDE.
All issues related to PlatformIO IDE should be reported to the
PlatformIO IDE for VSCode repository
Development Platform or Board.
All issues (building, uploading, adding new boards, etc.) related to PlatformIO development platforms
should be reported to appropriate repository related to your hardware
https://github.com/topics/platformio-platform
Feature Request.
Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose to keep the project small.
PlatformIO Core.
If you’ve found a bug, please provide an information below.
You can erase any parts of this template not applicable to your Issue.
Configuration
Operating system: Arch Linux
PlatformIO Version (
platformio --version
): PlatformIO Core, version 6.1.14Description of problem
The debugging scene has evolved in neovim with plugins like
nvim-dap
,nvim-dap-ui
andnvim-dap-virtual-text
.nvim-dap
supports the capability to loadlaunch.json
configurations in neovim as follows:This makes it possible to benefit from the efforts put into VS Code's debugger integration. However, when I try to execute the launch config
PIO Debug
,nvim
tells me that it does not have theplatformio-debug
adapter specified. I tried scouring a few repos on PlatformIO GitHub but could not find any mention about this adapter.I expected that correctly specifying the
platformio-debug
adapter would allow the debugger integration in PlatformIO as well. Here's how it looks, if you're wondering.https://github.com/mfussenegger/nvim-dap/wiki/Debug-Adapter-installation#ccrust-via-gdb
The text was updated successfully, but these errors were encountered: