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

Wokwi GDB VSCode launch not working #227

Open
OliverRhyme opened this issue Aug 2, 2024 · 1 comment
Open

Wokwi GDB VSCode launch not working #227

OliverRhyme opened this issue Aug 2, 2024 · 1 comment

Comments

@OliverRhyme
Copy link

Bug description

Running wokwi debugger via vscode does not work with error Unable to start debugging. The value of miDebuggerPath is invalid

  • Would you like to work on a fix? n

To Reproduce

Steps to reproduce the behavior:

prerequisites:

  • Setup wokwi vscode extension with license
  1. run cargo generate esp-rs/esp-idf-template cargo
  2. use these options
✔ 🤷   Which MCU to target? · esp32
✔ 🤷   Configure advanced template options? · true
✔ 🤷   Enable STD support? · true
✔ 🤷   ESP-IDF version (master = UNSTABLE) · v5.2
✔ 🤷   Configure project to use Dev Containers (VS Code and GitHub Codespaces)? · true
✔ 🤷   Configure project to support Wokwi simulation with Wokwi VS Code extension? · true
✔ 🤷   Add CI files for GitHub Action? · false
  1. open project in vscode
  2. reopen in dev container
  3. run cargo build
  4. run launch in vscode the "Wokwi GDB"

Expected behavior

Should be able to run wokwi gdb

Screenshots

N/A

Environment

  • OS: MacOS Sonoma
  • How did you install the environment: dev container

Additional context

@OliverRhyme OliverRhyme added the bug label Aug 2, 2024
@SergioGasquez
Copy link
Member

Hi! Since esp-12.2.0_20230208, gdb is no longer part of the official release that espup install, it now lives here so it needs to be separately downloaded and extracted on top of the current GCC toolchain location (/home/esp/.rustup/toolchains/esp/xtensa-esp-elf/esp-13.2.0_20230928 in the container).

That being said, I dont think we will work on fixing this at the moment, sorry.

@tomassebestik tomassebestik removed the bug label Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

3 participants