-
-
Notifications
You must be signed in to change notification settings - Fork 306
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
BUG: Debug process using "PIO Debug (skip Pre-Debug)" does not work as expected #477
Comments
It seems that part of the problem could be due to multiple installation of PIO core (the built-in one of VSCode, and a global one installed on the OS e.g. via pip command). But, while using "PIO Debug (skip Pre-Debug)", VSCode still want to build something (so if the program was edited, it will be built again) In this case, maybe "pre-debug" is not useful anymore ? Or maybe separate the "pre-debug" just to build the program in debug mode, without trying to launch full debug ? And then have a global option called "PIO Debug" which will check source files, build if needed, and launch debug ? |
I don't have a second PlO core. I fixed it for my project by editing I removed fields "projectEnvName" and "executable". Now the So I think the launch.json template seems to be the issue because the problem was with the automatically generated Edit: Nevermind. I cannot make it work anymore - code is built twice no matter what. |
After the platformio/platformio-core#4597 was fixed, now the remaining problem is letter drives on Windows when calculating a checksum. They are upper-case when running in the terminal and lower-case in debug console. Terminal:
Debug Console:
Platformio.ini:
Ah this should belong to PlO core issues. |
The thing just fixed itself. Not sure how because I did a few things. But it was probably related to the old version of
Strange, I don;t remember the warning until today installed One may have to go to |
Never mind, it didn't fix itself. I just forced the path using I created pio-core issue. |
Problem:
Using "PIO Debug (skip Pre-Debug)" in VSCODE does build sources again, instead of just launch debug. Same happened when using "PIO Debug" : sources are built twice (one time during pre-debug, the other one during debug).
Expected behaviour:
Does not build or check sources files when "PIO Debug (skip Pre-Debug)" is selected, as the documentation indicate.
Step to reproduce:
Create a simple PIO ini file like this one:
Build one time though VSCode.
Go to "Run" on the left, choose "PIO Debug (skip Pre-Debug)" in the list, and click on the run button. Building should start again.
If you run again "PIO Debug (skip Pre-Debug)", then it is fine. But if you choose "PIO Debug" next time, all sources are built twice again.
Infos:
Original discussion here.
Adding
build_type = debug
to force debug mode when building does not help.This problem does not seem to appear with other IDE, like CLION.
OS: Windows 10
VSCode: 1.52.1
PIO IDE Extension: 2.2.1
The text was updated successfully, but these errors were encountered: