You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AND the file "/home/russell/t2btrc" is empty, but created.
However, if I run
()1> redbug:start("erlang:term_to_binary", [{arity,
true}, {print_file, "/home/russell/t2btrc"}]).
{38,2}
()2> erlang:term_to_binary({my_tuple, is, boss}).
<<131,104,3,100,0,8,109,121,95,116,117,112,108,101,100,0,
2,105,115,100,0,4,98,111,115,115>>
redbug done, timeout - 1
()3>
In the node () the file is created and contains
16:49:39 <0.39.0>({erlang,apply,2}) {erlang,term_to_binary,1}
I expected running the rpc calls to result in the same outcome as running locally. Is this a bug in my thinking, redbug, or something else?
Both nodes are on the same physical host and have access to the file path.
The text was updated successfully, but these errors were encountered:
As reported here http://erlang.org/pipermail/erlang-questions/2018-November/096669.html
Start two nodes
in the second node () I run the following:
AND the file "/home/russell/t2btrc" is empty, but created.
However, if I run
I expected running the rpc calls to result in the same outcome as running locally. Is this a bug in my thinking, redbug, or something else?
Both nodes are on the same physical host and have access to the file path.
The text was updated successfully, but these errors were encountered: