dbg:trace does not work on remote shell

View: New views
3 Messages — Rating Filter:   Alert me  

dbg:trace does not work on remote shell

by Kaiduan Xie-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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?

Thanks,

kaiduan

________________________________________________________________
erlang-questions mailing list. See http://www.erlang.org/faq.html
erlang-questions (at) erlang.org


Re: dbg:trace does not work on remote shell

by Nicolas Charpentier-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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@localhost> dbg:tracer().
{ok,<XX,XX,XX>}
debug@localhost> dbg:n(first@localhost).
{ok,first@localhost}
debug@localhost> dbg:p(all,[c]).
{ok,[{matched,first@localhost,33},{matched,debug@localhost,34}]}
debug@localhost> dbg:tpl(....).


All the output will be done on the node debug@localhost.



Regards,

---
Nicolas Charpentier
http://charpi.net

________________________________________________________________
erlang-questions mailing list. See http://www.erlang.org/faq.html
erlang-questions (at) erlang.org


Re: dbg:trace does not work on remote shell

by Kaiduan Xie-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Nicolas,

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]).
{ok,[{matched,'debug1@...',0,{no_proc,<0.264.0>}}]}

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
application.

Thanks,

kaiduan

On Fri, Jul 3, 2009 at 2:51 AM, Nicolas
Charpentier<nc-dated-1251787914.f29799@...> 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@localhost> dbg:tracer().
> {ok,<XX,XX,XX>}
> debug@localhost> dbg:n(first@localhost).
> {ok,first@localhost}
> debug@localhost> dbg:p(all,[c]).
> {ok,[{matched,first@localhost,33},{matched,debug@localhost,34}]}
> debug@localhost> dbg:tpl(....).
>
>
> All the output will be done on the node debug@localhost.
>
>
>
> Regards,
>
> ---
> Nicolas Charpentier
> http://charpi.net
>

________________________________________________________________
erlang-questions mailing list. See http://www.erlang.org/faq.html
erlang-questions (at) erlang.org