Q:

Erlang dbg – Debugging on production OTP system with remote shell

I have an OTP based Erlang application that seems to behave weird.
I want to connect to the erlang shell and trace exactly what is happening.
I can do all my calls to dbg:tracer(), dbg:tp() etc. just fine, however no output is sent to my shell.
I think this might be, because I am connecting via a remote shell.
However, when I call dbg:n(wiwob@vlxd38-wob). I get an error:
** exception error: bad argument in an arithmetic expression
     in operator  -/2
        called as wiwob@vlxd38 - wob

How can I find out which shell the output is sent to and pipe it to my shell?

A:

The argument to dbg:n/1 must be an atom and wiwob@vlxd38-wob is not an atom, it needs to quoted like 'wiwob@vlxd38-wob'. For the syntax of an atom, and other data types, see Atoms.

