search

bmd-studio / stm32-for-vscode

STM32 extension for working with STM32 and CubeMX in VSCode
MIT License
208 stars 27 forks source link

launch.json debug config doesn't work #44

Closed dljsjr closed 3 years ago

dljsjr commented 3 years ago

Environment Info

Visual Studio Code Version: 1.52.1 stm32-for-vscode Version: 2.2.4 cortex-debug Version: 0.3.7 OS: macOS Big Sur 11.1 (Intel)

Bug Info

When running the built-in Build or Flash tasks, a launch.json gets generated for running debug configs. This config includes "preLaunchTask": "Build STM",, which is the offending line.

When running the debugger w/ this line present, VS Code times out after a few seconds with the following pop-up:

Screen Shot 2020-12-31 at 3 20 47 PM

Unfortunately, since there is no option to just truck on, VS Code kills the running task and the debugger never attaches.

Commenting out that line allows for debugging to proceed appropriately.

jortbmd commented 3 years ago

Hi,

My apologies for the late reply. This is some behaviour I have not seen before. The Build STM task should be able to be tracked. I could advise you to delete the task.json file and let it be generated again. If this does not fix the issue please let me know so I can look into it.

dljsjr commented 3 years ago

Hey there! Sorry myself for the late response! I tried that and it didn't seem to work. The only way to get it to work is to comment out that line and make sure I build by hand before debugging.

jortbmd commented 3 years ago

No worries,

Could you perhaps share your launch.json file and your task.json file? Or even better a project in which the error is reproducable? Does this happen on a specific project or various projects? Would be great if I had a way to produce the issue myself.

jortbmd commented 3 years ago

I have run into the issue myself now. This is due to an update of VSCode itself and the way it handles tasks. There currently is a standard output for non tracked tasked. Tracking seems to just be declaring what the end of stdout needs to be for when the tasks is complete. I first will finish up some major refactoring and feature additions and than I will look into this.

dljsjr commented 3 years ago

@jortbmd That's good news, I totally forgot to send you my tasks.json and I apologize!

jortbmd commented 3 years ago

I think I have fixed the problem in version 3.0.0. There was an issue were the build task would not complete (an unresolved promise). This has been fixed and I haven't encountered the tracking issue any more. Should this pop up again feel free to open another issue. For now I am closing it.