Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 5.6.X, 2017.1.X, 2017.2.X
Votes
1
Found in
5.6.1f1
Issue ID
912607
Regression
No
Visual Studio throws the "Unable to step" error when stepping over the code
Steps to reproduce:
1. Open the attached project (DebuggingBug.zip)
2. Open the test scene
3. Open the test.cs script in Visual Studio 2015/2017
4. Put a breakpoint on the lines 10 and 14
5. Attach to Unity and Play
6. Inspect the variable r when the breakpoint is hit
7. Step over until you will get an error
8. Observe the error:
Unable to step. Operation is not supported
Expected result: You should be able to debug the code
Actual result: Visual studio throws the error message
Reproduced with: 5.4.5p2, 5.5.3p4, 5.6.1p1, 2017.1.0b6
Fixed in: 2017.3.0b1
Bacported to: 5.6.3p4, 2017.1.1p2, 2017.2.0b11
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
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
- Graphics.DrawProceduralIndirect and Graphics.DrawProceduralNow silently dropped on DX12
sailro
May 30, 2017 21:37
With 2017.1.0b7 it works as expected with the new experimental runtime (same issue with the legacy one). But if you try to stop/start the game several times, Unity will crash. (perhaps another unrelated issue).
sailro
May 30, 2017 20:48
I am able to reproduce this behavior both with VSTU and MonoDevelop. So it seems to be an issue with the stepping on the Unity side.