[erlang-questions] How to debug erlang

[Schneider]

Chapter 17 in Erlang Programming by Francesco Cesarini and Simon Thompson gives a good introduction. However, Erlang debugging and tracing does require quite some understanding of the system before you can use it effectively. It is hugely effective if you know what you’re doing, so read the book first, which dates back some ten years but is still well worth reading.
Another very useful tool is the observer. Start with observer:start() from the Erlang shell.
The other tool to use as a beginner is the GUI debugger. Start from the Erlang shell with debugger:start(). See the Erlang docs for it’s use. This is probably more inline with the tools you’re used to.

Frans

> Op 19 jun. 2019 om 16:57 heeft Garrett Smith <g@REDACTED> het volgende geschreven:
> 
> 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:
>> 
>> Hello all,
>> 
>> another beginner question: Is there any good description of how to
>> debug Erlang applications? My current problem is cowboy on a Raspberry
>> Pi - even the hello_erlang from the guide doesn't process requests, but
>> I'd rather like to learn how debugging is possible at a more general
>> level.
>> 
>> Thanks in advance,
>> Eckard
>> 
>> --
>> Wir haften nicht für die korrekte Funktion der in dieser eMail
>> enthaltenen Viren. We are not liable for correct function of the
>> viruses in this email! :)
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions