Search Issue Tracker
Fixed
Fixed in 2021.3.9f1, 2022.1.16f1, 2022.2.0b8, 2023.1.0a6
Votes
0
Found in
2021.3.6f1
2022.1.9f1
2022.2.0a19
2023.1.0a3
Issue ID
UUM-9132
Regression
Yes
Unable to hit breakpoint in Visual Studio when debugging IL2CPP Build
How to reproduce:
1. Open the attached project "BreakpointsIssue.zip"
2. Open Assets/Scenes/SampleScene.unity
3. Open Assets/TestClass.cs
4. Put a breakpoint at line 35 in Visual Studio
5. Open File>Build Settings... in the Editor
6. Enable Development Build
7. Enable Script Debugging
8. Build And Run the project
9. Open Debug>Attach Unity Debugger in VS
10. Select "BreakpointsIssue"
11. Press OK
12. Press Space in the Player
Expected results: Line 31 is hit in VS
Actual results: Line 31 is marked as "Unable to find a corresponding location"
Reproducible with: 2021.2.0a12, 2021.3.6f1, 2022.1.9f1, 2022.2.0a19, 2023.1.0a3
Not reproducible with: 2020.3.37f1, 2021.2.0a11
Reproducible on: Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
- Sub-State machine “breadcrumb trail” doesn’t fit in the window if there’s too many Sub-State machines
Add comment