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

Notification

Icon
Error
Debug hangs after enabling .NET Framework source stepping
Options
Previous Topic Next Topic
RobertTheGrey
#1 Posted : Tuesday, September 8, 2015 3:19:04 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 7/10/2012(UTC)
Posts: 6
Location: UK

Thanks: 3 times
In VS2015 I was debugging one of my tests just fine, but was getting a NULL ref exception from inside external framework code on one of my lines. So in debug options I ticked "Enable .NET Framework source stepping" which disables the "Just My Code" option and should allow me to step through symbol source. Since ticking that box, and I try "Break into test at this line" VS2015 hangs and I have to end task on it. Worse than that, I unticked the box to put it back the way it was and NCrunch now hangs on any test I try and break into - so basically I can't ever debug anymore even though I've restored the setting back to the way it was.

I tried to change my projects from "Any CPU" to x86, and tried again but it hung. I changed to x64 and this time I got the dialog saying that the process is taking to long, would I like to terminate the remote session, and then when I terminated it, VS2015 cam back fine - didn't need to kill the process.

But still no luck debugging via NCrunch after multiple restarts. Any help much appreciated, even if it's just a way to reset it back to the way it was.
Back to top
Remco
#2 Posted : Tuesday, September 8, 2015 9:47:25 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi, thanks for sharing this issue.

I suspect there may be an issue with the debugger itself in VS2015. NCrunch doesn't really do much with the debugger other than ask it to attach to an existing process. There is another user that has reported a similar issue, which eventually was reported to MS and the team has acknowledged it to be a problem with the debugger. See for more information - http://forum.ncrunch.net/yaf_postst1622_Unable-to-Debug-tests-in-Visual-Studio-2015.aspx.

Something that may be worth trying is to perform a full reset of your VS configuration to see if there is something in the registry hive that is triggering the problem. When launching VS, try running 'devenv.exe /rootsuffix test'. This will make VS use a different registry hive for the session, effectively making it work temporarily with all configuration reset. If this doesn't work, it may be worth trying to reinstall Visual Studio (sorry, I know its painful, but we really don't know what's broken in there).
Back to top
1 user thanked Remco for this useful post.
RobertTheGrey on 9/9/2015(UTC)
RobertTheGrey
#3 Posted : Wednesday, September 9, 2015 10:56:07 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 7/10/2012(UTC)
Posts: 6
Location: UK

Thanks: 3 times
Thanks Remco - seems my entire debugger was broken by something. I couldn't debug with R# or run my web project any more either - only after a VS repair did the debugger start working again.
Back to top
Remco
#4 Posted : Wednesday, September 9, 2015 11:02:51 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
I'm glad a rebuild fixed the problem! No idea what happened here, but it's good that you're back up and running :)
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.034 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download