How to find out what's going on

Per Hedeland <>
Wed Jan 4 01:36:22 CET 2006


Joel Reymont <> wrote:
>
>22:52:46: <0.32.0>: Received: 0.000797s: srv_table_state
>22:53:08: <0.32.0>: Received: 0.000110s: {srv_table_state, ...}
>
>You can see a difference of 22 seconds above. Normally this would not  
>be cause for concern but the two traces are from two consecutive  
>lines in the same module!
>
>	    trace(Bot, 90, "Received: ~.6. fs: ~p",
>		  [Seconds, Cmd1]),
>	    trace(Bot, 80, "Received: ~.6. fs: ~p",
>		  [Seconds, element(1, Cmd1)]);

Hm, are you sure? Seems to me the that if the first line was logged
by the first trace call, the second trace call would have caused a
badarg (from element(1, srv_table_state)). I.e. unless you did some
copy'n'paste mistake here, it's more likely that the first line is
logged by the second trace call, and the second line is logged by the
first trace call the next time you run through this particular piece of
code - we sure don't know what happened in between.:-)

--Per Hedeland



More information about the erlang-questions mailing list