4
Vote

Debugging/set breakpoint slow with increasing LoC

description

Hi,

I'm using the .NET MF 4.3 with a Netduino Plus(N+) and Netduino Plus 2(N+2).

Problem description

With my current project I made the experience that setting a breakpoint in VS2012 Premium takes seconds when using the N+2. Debugging the same code on the older N+ just works fine.
The main difference between both is the "cpu"

Steps to reproduce

I tried different ways and found out the following, which can be observed on the N+2.
  1. When debugging a simple app with only one class and less than 100 LoC setting the breakpoint happens immediatly and the breakpoint is also hit.
  2. While debugging a simple app with about 10 classes and 400-500 LoC in one project, setting breakpoints already takes more time and as soon as a breakpoint is hit and you try to observe an objectinstance with by hovering over it, takes a few seconds to open a property and display its property values.
  3. The last I tested was my acutal project spread over 3 projects with more than 500 LoC (maybe 1000) and about 30 classes. Setting a breakpoint in VS2012 took seconds from the click until the red dot was shown and until now none of them where ever hit...
==> For all three test only one single breakpoint was defined and the project properties were the default ones, except I had to switch to target framework 4.2 (because of the SDK support for the hardware). Just added my classes and required references.

On the other hand on the N+ it doesn't matter how much code or how many breakpoints I'm setting
everything works fine, defining also multiple breakpoints in multiple classes is no problem. Even if there are 4 threads running handling a lot of data. It just works.

So the strange part is that the faster model is getting slower to unresponsive with increased LoC and the slower/older always works fine. Is this maybe related to the new microcontroller?

I already opened a ticket to the Netduino support and they told me, that they assume it's related to the .NET MF

If you need more information, or if you have suggestions what I should try, just give me short reply!

comments

awaiK wrote Feb 7, 2013 at 3:40 PM

I think it would be helpful to provide three different Visual Studio Solutions, to reproduce the above.

TechInfo wrote Feb 8, 2013 at 12:55 AM

I'm experiencing the same problem with Netduino Plus 2 using the modbus demo:

http://cetdevelop.codeplex.com

V2 in the source code
Cet\IO\Cet.IO.DemoModbus\Cet.IO.DemoModbus_MF42.sln

Debugging (watch/break point) is slow as hell... not responsive using VStudio 2012 Pro.

nielshebling wrote Feb 8, 2013 at 9:53 AM

I try to provide three different solutions.
Because at least for the last test code I tried additional hardware is required.

zeroaviation wrote Aug 28, 2013 at 6:46 PM

I too have this issue. No resolution yet.