Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.8f1
Issue ID
1074484
Regression
No
Breakpoints are ignored in VS Code if you first start debugging in VS Code and then enter Play mode
To reproduce:
1. Open the attached project (CyberSidescrollerRefactored.zip)
2. Open the TestItems scene
3. In VS Code, add a breakpoint on the line 11 in the ItemUseTester
4. Start Debugging in VS Code and Enter Play mode
5. Press Use E-Tank button in the game
6. Observe that the breakpoint wasn't hit
7. Stop debugging and exit Play mode
9. Enter Play mode and then Start Debugging
10. Step 5.
11. Observe that the breakpoint was now hit
Expected: breakpoints aren't ignored no matter in what order the debuggin process and Play mode were started
Reproduced in 2017.3.2f1, 2017.4.10f1, 2018.1.8f1, 2018.1.9f2, 2018.2.6f1, 2018.3.0a10
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Missing `localhost` in the `hosts` file configuration could cause the Unity Package Manager server to fail to start
- Wrong scaling in shadow mask scene view mode
- Type.GetField() works differently in IL2CPP from Mono
- Splitter resize cursors flicker on Linux and Windows
- Can't select sRGB color format for Render Texture on HDRP project
Resolution Note:
This is not a Unity problem, but a problem with the debugger extension for Visual Studio Code.
The code is maintained here: https://github.com/Unity-Technologies/vscode-unity-debug/
And the problem has been addressed already.