> Regarding stack traces, it turns out you don’t need them. goes on to suggest rolling your own buggy, slow, informally specified implementation of half of a s

> Regarding stack traces, it turns out you don’t need them. goes on to suggest rolling your own buggy, slow, informally specified implementation of half of a stack trace printer