[erlang-questions] Tracing and debugging
Fernando 'Brujo' Benavides
Tue Jan 13 13:48:30 CET 2015
I think that’s pretty close to what redbug <https://github.com/massemanet/eper/blob/master/doc/redbug.txt> does. I use redbug for debugging purposes in almost all of my projects. In fact, eper is one of my “default dependencies”, together with lager and sync :)
Fernando "Brujo" Benavides
> On Jan 13, 2015, at 09:36, 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,
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions