Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.2.X
1.3.X - Entities
7000.0.0a1
Issue ID
ECSB-1091
Regression
Yes
Breakpoints in code can not be reached when they are placed below a comment
How to reproduce:
1. Open the attached “breakpoints_issue” project
2. Open the "SampleScene" and enter Play mode
3. Observe that the Console window prints messages containing “true” and “false”
4. In the Project window, double-click the “MySystem” script found in the “Assets” folder to open the file in Visual Studio
5. In the menu bar of Visual Studio, ensure the configuration is set to “Debug”
6. Press the “Attach to Unity” button
7. Add breakpoints on the two lines containing “Debug.Log” statements (right-click → Breakpoint → Insert Breakpoint)
8. Observe the result
Expected result: No warnings occur
Actual result: A warning stating “The breakpoint will not currently be hit. Unable to find a corresponding location“ is shown at the second breakpoint
Reproducible in: 1.1.0-exp.1 (2022.3.28f1), 1.2.1 (2022.3.28f1, 6000.0.2f1)
Not reproducible in: 1.0.16 (2022.3.28f1)
Could not test with: 2021.3.38f1 (Entities is not supported)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
* The reproduction instructions from step 5 onwards assume that Visual Studio is used as the code editor
* Reproduced in Visual Studio 2022 and Visual Studio Code 1.87
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
- Sprite Importer Checkbox Label Truncated in UI (2D Template)
- Light theme icon is missing for Volume Component in the Inspector window
- Volume Profile effects are still showing and active in Game View when the Volume Profile is reset
- Shader Graph Tab Lacks Right Margin for Long Titles
- 2DLight component only renders when ShadowCaster2D components are within range in WebGL builds
Resolution Note:
Fixed by another internal issue: ECSB-1446: Debugger stops at commented lines of code when using ECS