Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
Debugging With NCrunch Doesn't let me see values of vars
Options
Previous Topic Next Topic
nguyette
#1 Posted : Thursday, May 10, 2018 5:03:55 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 5/8/2018(UTC)
Posts: 8
Location: United States of America

Thanks: 2 times
Was thanked: 1 time(s) in 1 post(s)
Using MSTest and NCrunch for debugging, I cannot hover over variables to see their values. Is this a bug?
Back to top
 |  Edit by user
Remco
#2 Posted : Thursday, May 10, 2018 11:27:26 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,976

Thanks: 931 times
Was thanked: 1257 time(s) in 1170 post(s)
Hi, thanks for sharing this issue.

Do you notice this with ALL variables in all methods? Do any of your locals work correctly?
Back to top
nguyette
#3 Posted : Friday, May 11, 2018 1:42:42 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 5/8/2018(UTC)
Posts: 8
Location: United States of America

Thanks: 2 times
Was thanked: 1 time(s) in 1 post(s)
No, it is not for all variables. I hovered over an int[] and I was able to see the values inside, but not for a List<string>. Just to test this issue, I assigned an int named "A" the value of 4. I could not see the value of A by hovering over it.
The way I got to this point is by right clicking on the left margin > Advanced > Debug covering test in existing task runner...

If I use the standard MSTest debugging, I'm able to see all the values of these variables.

This is on Windows 10 Pro, Version 1709, Build 16299.371.

Visual studio:
Professional 2017
Version 15.7.1

NCrunch:
Company Seat License
Version 3.15.0.6
Back to top
 |  Edit by user
Remco
#4 Posted : Friday, May 11, 2018 11:12:45 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,976

Thanks: 931 times
Was thanked: 1257 time(s) in 1170 post(s)
It's possible that this is caused by a metadata issue with the PDBs. Previously, where we've seen these problems it's been related to compiler generated structures such as async/await and yield. If you're able to isolate this problem in code that you can share with me, I can take a closer look to try and understand it better.

Unfortunately, the debugger is a bit of a black box to us. Even when the PDB structure is correct, sometimes weird things can happen in certain environments. Reproducing these problems with consistency can often prove difficult to do.
Back to top
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.033 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download