4 ms·
> All of those are useful. But none of them tell you where the code broke. Good logs do
by 18172828286177 1y ago
> All of those are useful. But none of them tell you where the code broke.
Good logs do
- vanschelven 1y agoFor some definition of "where" :-) it's my experience that a full stacktrace is needed (or at least super-helpful) when debugging, since the innermost (triggering) level is not always the level where the problem was introduced. Getting full context (including the values of local variables) all the way up the stack makes that puzzle a whole lot easier.