[erlang-questions] Tracing and debugging

Vladimir Ralev vladimir.ralev@REDACTED
Tue Jan 13 13:56:00 CET 2015

Further it will be awesome if there is a UI debug tool where you can
step through the code on a timeline based on the generated logs
without having to read them. Java has Chronon debugger which works
sort of this way but records more metadata due to the nature of Java.
In Erlang it will be easier.

On Tue, Jan 13, 2015 at 2:36 PM, Vlad Dumitrescu <vladdu55@REDACTED> wrote:
> Hi all!
> I just got a crazy idea and I think it's not that crazy, but I'm willing to
> get feedback on that :-)
> The main reason I use the debugger is to check that the intermediary values
> in a computation are the expected ones. The alternative (which works without
> messing up timeouts) is to print out values at points of interest, but it is
> messy (there's a lot of boilerplate to type and the interesting code becomes
> hard to read).
> So, I thought, what if, instead of interpreting a module in order to debug
> it, we compile it with a special parse transform that inserts tracing calls
> after each expression in the code, automatically keeping track of the
> variables visible in the scope and their values?
> The output can be via io:format, et:report_event, or something else
> (configurable).
> Could this "trogging" or "logtracing" be useful, or am I delusional? Maybe
> there already is such a thing, the Erlang ecosystem is getting difficult to
> keep in the working memory :-)
> best regards,
> Vlad
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

More information about the erlang-questions mailing list