0

I wanted to step through and study MS implementation of data structures in System.Collections.Generic. Setted-up Visual Studio 2015 debugger to options you see below.

First issue: while trying to step into LinkedList<int> list = new LinkedList<int>(); debugger steps over LinkedList constructor. This particular constructor is empty. Is this a default behavior of VS debugger to step over empty constructors ?
Second issue: debugger steps over internal LinkedListNode(LinkedList<T> list, T value) constructor, instead of stepping in.
How do I force debugger to step into constructors ?

enter image description here enter image description here

newprint
  • 6,936
  • 13
  • 67
  • 109
  • The reference source symbol server is *very* slow to get updated. You probably have .NET 4.6.2 on your machine right now, a version that it doesn't have yet. You can only get a PDB from the msdl server but that one doesn't have source info. You can see the debugger fail to get the PDB using [this procedure](http://stackoverflow.com/a/27655501/17034). – Hans Passant Nov 06 '16 at 12:47
  • @newprint, would you please share the latest information about this issue? – Jack Zhai Nov 14 '16 at 11:50

2 Answers2

0

Have you looked here: How to: Debug.Net Framework Source

Make sure you have the symbols loaded

Andrew McClellan
  • 52
  • 5
0

I debug it in my side, it couldn't step into the LinkedList even if I use the correct debugging .NET framework source code steps here, actually if I use the "Go To Definition" and visit the System.Collections.Generic.LinkedList, I also could step Into it even if I add a breakpoint firstly, so I think we couldn't step Into it.

enter image description here

Jack Zhai
  • 6,230
  • 1
  • 12
  • 20