[erlang-questions] How to debug erlang

Eckard Brauer eckard.brauer@REDACTED
Wed Jun 19 19:36:58 CEST 2019

Hello Oliver and Garret,

thank you for the helpful hints - indeed, I already found "Erlang in
anger", but didn't read it at the time - so I simply didn't remember.
The recon_trace I will definitely have a look on.

One more question: I believe to remember that I read at any occasion of
a possibility to create a backtrace from within a code snippet, but
didn't try it aut extensively at that moment, so I forgot about. Do you
have one more hint for that - or did I mix up things with any other


Am Wed, 19 Jun 2019 09:57:19 -0500
schrieb Garrett Smith <g@REDACTED>:

> I suggest getting into the habit of using tracing. It's one of
> Erlang's game changing features.
> In a pinch, print to stdout. But once you become proficient at
> tracing, it's very fast.
> I've been doing a lot Python programming lately (machine learning) and
> miss the ability to observe a program without a) modifying it or b)
> tediously stepping through code.
> I haven't use this but based on the author I already know it's
> excellent :)
> https://ferd.github.io/recon/recon_trace.html
> Perhaps there are others folks can recommend. I personally found the
> built-in dbg interface quite complex and wrote something for e2.
> Garrett
> On Wed, Jun 19, 2019 at 9:25 AM Eckard Brauer <eckard.brauer@REDACTED>
> wrote: [...]


More information about the erlang-questions mailing list