Stack Traces in Debugging
Comments discuss the importance, limitations, and alternatives to stack traces for error debugging across languages like Go, Python, JS, and Rust, including tools for capturing and improving them.
Activity Over Time
Top Contributors
Keywords
Sample Comments
this seems a jillion times better than a standard stacktrace. why isn't it in built into the core?
Cool idea! Does it give me a stacktrace of exceptions too?
I don't understand there are no stack traces unless you use a library?
Other languages have stack traces, so you don't have to reinvent the wheel in an inferior manner.
Printing stack traces generates a lot of useful context but it's not done enough.
Shouldn't it be easier to debug, because you have stack traces?
Does this not give you working stack traces?
You should be able to get stack traces in the debugger, what issues did you run into?
I'd suggest looking at backtrace.io It may be overkill for what you want to do, but one thing it does really well is to log stack traces.
I don't see why anyone would find this superior to a stack trace.