none
Why is the arrow in the Visual Studio debugger *after* the current function call when you go up the stack?

    Question

  • When you are executing code, it makes sense to have the arrow pointing to the instruction that will be executed.

    But when going up the stack, it would make more sense for the arrow to point to the function we are in, rather than the next one. 

    Monday, July 18, 2016 6:55 PM

Answers

  • When you are executing code, it makes sense to have the arrow pointing to the instruction that will be executed.

    But when going up the stack, it would make more sense for the arrow to point to the function we are in, rather than the next one. 

    Not that sure about it. Probably one could argue, call-instruction was already executed in the context/scope of this stack-frame and as you mentioned, instruction pointer points to the next instruction to be executed by convention.

    With kind regards


    Tuesday, July 19, 2016 8:56 AM