I seem to be having an issue using the call stack viewing functionality of Microsoft Visual Studio 2010 Professional.
During debugging, my application crashed, so I inspected it with the call stack view.
The offending line was contained within called showInDGV(...) nothing exciting, just trying to read an uninitialized variable or something...
All well and good, so next thing I did was check to see where the call to showInDGV() was coming from, because it is called from multiple places.
When double clicking the entry in the call stack (the entry that should highlight a showInDGV(...) subroutine call), the IDE highlighted the incorrect line.
Instead of highlighting showInDGV(), it highlighted the next non-empty line below it, which was End Sub
Clearly something is wrong here....
So I inspected the call stack further - turns out Visual Studio is highlithing the wrong line whenever I try to debug using the call stack.
This isn't actually the first time this has happened. In fact, it seems to always happen when working on a large project.
Initially, the call stack works properly and highlights the correct line, but at some point it gets messed up, and then it never seems to fix itself, even after closing and re-opening the program.
Does anyone know the cause/solution to this issue? I figure it might be some sort of corruption in the visual studio project, and I considered copying and pasting the source code into a new project but even if that fixed it, it wouldn't prevent it from happening again.
