Difference between native frames of !dumpstack and k

Question

I'm a developer but I've been seconded into a support role which, because of my development experience, mostly involves analysing crash dumps using windbg. I'm pretty confident doing this now but one thing I've been wondering is why there are many more native frames in the output of !dumpstack than there is in the output of the k commands. Isn't !dumpstack supposed to output the native stack interleaved with the managed stack?

Answer 1

in short, k walk frame pointer under x86, virtually unwind under x64, sos!dumpstack dump every possible code pointer (in executable page) sos can find on native stack space