Search Issue Tracker
Fixed
Votes
2
Found in
4.3.0b3
Issue ID
568430
Regression
No
Step-Over skips the whole body of switch statement
Steps to reproduce :
- create a new project
- import the script attached
- create a new game object and attach the script to it
- attach the debugger and set a breakpoint in the Update function
- press play and in Mono Develop press step over and notice that it skips the switch statement
Comments (1)
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
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
CrazyDef
Sep 02, 2014 06:44
From what I've seen debugging is basically broken in Unity. You can't single step more than a few lines before Unity just starts running again. I'm using UnityVS as my primary debugger, but MonoDevelop doesn't work any better. The guys at Microsoft (who own UnityVS these days) are blaming an ancient scripting engine within Unity. So, Unity... when are you going to upgrade?