4 ms·
I will usually plop a breakpoint at where the problem is presenting itself (often in a controller or view), scan up the stack to find where I think the problem
by ehnto 7y ago
I will usually plop a breakpoint at where the problem is presenting itself (often in a controller or view), scan up the stack to find where I think the problem is actually being caused, then break at that point and walk through the code as you suggest.
If I understand the application really well often I don't need to do the first step, but it can be a handy shortcut.