[erlang-questions] dbg:trace does not work on remote shell

Kaiduan Xie kaiduanx@REDACTED
Sat Jul 4 04:40:19 CEST 2009


This does not work out. When I type the dbg:p(list_to_pid("<0.X.0>"), [c, m]),

4> dbg:p(list_to_pid("<0.264.0>"), [c, m]).

Process <0.264.0> is on running OTP application.

Also I am attaching an remote shell to the running OTP application
with -remsh, this remote shell is a local shell on the running OTP



On Fri, Jul 3, 2009 at 2:51 AM, Nicolas
Charpentier<nc-dated-1251787914.f29799@REDACTED> wrote:
> Kaiduan Xie wrote:
>> This is another question on dbg, it looks weird.
>> If I start an OTP application in the shell, the trace works well.
>> However, if an remote shell is attached to the running OTP application
>> using -remsh (Remote shell is running on the same machine), trace does
>> not work. There is no output of the trace on remote shell.
>> Any idea?
> Hi,
> The output of dbg is done on the standard output of the first node. Dbg
> tracer that you have started use the group leader of your orininal node.
> If you need to have the output on the second node you can use dbg:n/1 to
>  add all the node where trace pattern have to be activated.
>  Start the first node.
> $ erl -sname first
> $ erl -sname debug
> debug@REDACTED> dbg:tracer().
> {ok,<XX,XX,XX>}
> debug@REDACTED> dbg:n(first@REDACTED).
> {ok,first@REDACTED}
> debug@REDACTED> dbg:p(all,[c]).
> {ok,[{matched,first@REDACTED,33},{matched,debug@REDACTED,34}]}
> debug@REDACTED> dbg:tpl(....).
> All the output will be done on the node debug@REDACTED
> Regards,
> ---
> Nicolas Charpentier
> http://charpi.net

More information about the erlang-questions mailing list