views:

3867

answers:

3

I ask because I couldn't find the stack trace in Visual Studio, while debugging an exception that occurred, after 30 seconds and didn't know to initially google for "Call Stack Window".

And now via the magic of StackOverflow and Google, I won't ever have to remember again. Though through the act of writing this, I will never forget. Isn't it ironic?

+9  A: 

While debugging, Debug/Windows/Call Stack

cdonner
+4  A: 

The default shortcut key is Ctrl-Alt-C.

Brian Rasmussen
It's important to note that you must be in 'debug' mode to see the call stack window.
dss539
+2  A: 

Do you mean finding a stack trace of the thrown exception location? That's either Debug/Exceptions, or better - Ctrl-Alt-E. Set filters for the exceptions you want to break on.

There's even a way to reconstruct the thrower stack after the exception was caught, but it's really unpleasant. Much, much easier to set a break on the throw.

Ofek Shilon