Using trace and dbg in Erlang
- by Gordon Guthrie
I am trying to start using erlang:trace/3 and the dbg module to trace the behaviour of a live production system without taking the server down.
The documentation is opaque (to put it mildly) and there don't appear to be any useful tutorials online.
What I spent all day trying to do was capture what was happening in a particular function by trying to apply a trace to module:function using dbg:c and dbg:p but with no success at all...
Does anyone have a succinct explanation of how to use trace in a live Erlang system?