Search Issue Tracker
Won't Fix
Votes
0
Found in
5.5.0f3
Issue ID
865975
Regression
Yes
Visual studio 2015 debugger not showing variable values within different scope while debugging the coroutines
Steps to reproduce:
1. Open the attached project (865975-TestProject.zip)
2. Open the test.unity scene
3. Open script(Assets/TestScript.cs) in Visual Studio and attach debugger to Unity process.
4. Set break point on line 13
5. Press play in Editor
6. When debugger stops on a break point press press "step over" or "step in" three times, so that the debugger would be evaluating line 16
7. Hover over the aa or qq
8. Notice, debugger does not evaluating these variables
Expected result: Variables should be evaluated
Actual result: Debugger does evaluate the variables
Reproduced with: 5.5.0a4, 5.5.0f3, 5.5.0p3, 5.6.0b3
Not reproduced with: 5.3.7p3, 5.4.3p4, 5.5.0a3
Regression introduced in 5.5.0a4
------------------------------
This issue needs be resolved within Visual Studio Tools for Unity (VSTU). We have contacted them about this issue and they are actively looking into resolving it.
Comments (2)
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
- Editor crashes and a window with "GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)" error is shown when launching a freshly created project
- Editor Windows dragging behavior is erratic/glitchy when a specific multi-display setup is used and the Editor window is not on the main display
- Meta Quest missing an icon in Build Profiles window in U6.0
- Foldout arrow indent is misaligned in the Inspector when used for Arrays or Lists
- Material import pipeline strips properties when it is added with a script
lionheartt
Apr 13, 2018 09:06
When will they fix this?!!!
tswierkot
Jan 08, 2018 16:19
When will they fix this?