[erlang-questions] Fwd: erlang:trace/3 and cpu_timestamp

[mats cronqvist]

  tracing with high-resolution timers doesn't seem to work un my linux
boxes (centos6, in this case);

247> erlang:trace(all,true,[call,cpu_timestamp]).
** exception error: bad argument
     in function  erlang:trace/3
        called as erlang:trace(all,true,[call,cpu_timestamp])

  Seemingly, this is because this check in aclocal.m4;

   case $host_os in
       linux*)
           AC_MSG_RESULT([no; not stable])
           LIBRT=$xrtlib
           ;;

  Indeed, commenting out the above and rebuilding beam works;

1> erlang:trace(all,true,[call,cpu_timestamp]).
24

  Is there any reason not to enable this?

  mats
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140424/6b237718/attachment.htm>