I also have similar problem with VS 2008 (and SP1 as well). debugging
unmanaged C++ heavily-templated code
is very very slow. Stepping either in source window or in disassembler takes
several seconds. Closing Auto, Locals and Watch does not help (but it lowers the delay to some point). Only a single breakpoint (or no breakpoints at all) is defined.
Another problem with heavily templated code is that it looks like a Disassembler window has an internal limit on maximum identifier length, so when a "call" instruction is displayed that refers to a particular long identifier name, no identifier name, and even no address is displayed - just the "call" instruction itself!
This problem, and slow
down did not occur in VS 2005.
The interesting part is that sometimes, if during debugging I switch to another window, do something, switch to something else etc. and then switch back to the pending debugger, it starts working
as a rocket! Like it was some lock a debugger had to acquire each step and now it is gone!
being debugged does not do or initiate any network or inter-process communications, it's just a simple console
And to finish a "bug report" - starting from SP1 command "Step to cursor" crashes the Visual Studio.
OS - Windows XP.