[erlang-patches] Attempt at making stacktraces more readable
Anthony Ramine
n.oxyde@REDACTED
Sun May 5 15:45:09 CEST 2013
Hello,
When an error isn't caught by a catch expression, the VM sends the faulty stacktrace as a string with a small message to the error logger. As it is already a string representation and not the stacktrace itself, the result may as well be readable and human-friendly. This is an attempt at making exactly this.
I have no idea how this will be received by the community, I'm just trying to spark a discussion about how we could improve the way stacktraces are currently printed.
To choose a format, Rosetta Code was my main source of inspiration [1].
git fetch https://github.com/nox/otp.git better-error-reports
https://github.com/nox/otp/compare/erlang:maint...better-error-reports
https://github.com/nox/otp/compare/erlang:maint...better-error-reports.patch
Regards,
[1] http://rosettacode.org/wiki/Stack_traces
--
Anthony Ramine
More information about the erlang-patches
mailing list