Reputation: 375
I fairly often get to a state in VS (C#) debug breakpoint or exception where I want to exit out of several levels of method to a caller a few levels up the stack. I can then patch up/retry/etc.
In simple cases I can [1] find the end of the current method, [2] set next statement, and [3] step out. Then repeat 1/2/3 working my way up the calling stack till I get where I want to be. However, this is a decided pain ....
Can anyone suggest any automation to help this? In order of preference ....
(I've tried searching, but all the terms I can think of are so generic that I haven't got any useful answers).
Upvotes: 5
Views: 3759
Reputation: 5132
The debugger does not have a way to set the next statement to execute somewhere other than the current method at the top of the stack.
Upvotes: 2