search

zero-plusplus / vscode-autohotkey-debug

https://marketplace.visualstudio.com/items?itemName=zero-plusplus.vscode-autohotkey-debug
53 stars 4 forks source link

Debug ignoring specified runtime path? #305

Open SAbboushi opened 12 months ago

SAbboushi commented 12 months ago

Hi- I'm now upgrading from AHKv2 alpha and your extension to current versions. Have been unable to get your debugger adapter to work again after the upgrades. NOTE: I am running portable versions of vscode and autohotkey v2.

My launch settings are in my workspace's .code-workspace file (in my case, AHKv2.code-workspace): image

But when I start debug, I get this error: image

We've spoken earlier about your extension supporting the settings in .code-workspace file: https://github.com/zero-plusplus/vscode-autohotkey-debug/issues/62#issuecomment-792113520 https://github.com/zero-plusplus/vscode-autohotkey-debug/discussions/117#discussioncomment-1221324

I'm wondering whether I have misconfigured something or whether there is some reason the extension is not recognizing/honoring the runtime setting in .code-workspace file? It's been a couple of years since I was actively programming/debugging my AHK scripts, so I may be doing something silly...?

SAbboushi commented 12 months ago

Note: when I click on "Open 'launch.json'" button in the error message window, vscode opens my AHKv2.code-workspace file

zero-plusplus commented 11 months ago

I have checked that the runtime attribute works in two different ways: when set to launch in code-workspace and in .vscode/launch.json in the workspace folder, but no issue occurred.

The error shows that the default path is set for runtime, so it does not appear to be a path specification error.

At the moment I can only advise you to make sure that you have specified the debugging configuration correctly.

I decided to improve the messages so that when an error occurs, it is possible to determine which debugging configuration is specified. You can track it here.