Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix vscode error invalid miDebuggerPath for esp32 #2921

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

mikee47
Copy link
Contributor

@mikee47 mikee47 commented Dec 12, 2024

The make ide-vscode script generates the default launch.json configuration, containing the following entry:

"miDebuggerPath": "${env:IDF_TOOLS_PATH}/tools/riscv32-esp-elf-gdb/12.1_20231023/riscv32-esp-elf-gdb/bin/riscv32-esp-elf-gdb"

The error occurs where IDF_TOOLS_PATH isn't available in the global environment. There does not appear to be a way to include definitions for environment variables other than within the configuration itself, which renders it pointless. Since IDF_TOOLS_PATH is very unlikely to change we can just use the expanded path:

"miDebuggerPath": "/opt/esp32/tools/riscv32-esp-elf-gdb/12.1_20231023/riscv32-esp-elf-gdb/bin/riscv32-esp-elf-gdb",

@SmingHub SmingHub deleted a comment from what-the-diff bot Dec 12, 2024
@slaff slaff added this to the 6.0.0 milestone Dec 12, 2024
@slaff slaff merged commit c1d5b9d into SmingHub:develop Dec 12, 2024
35 checks passed
@mikee47 mikee47 deleted the fix/esp32-debugger-path branch December 12, 2024 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants