title: What is difference between "node --prof" and using node-profiler
body: <p>I'm trying to profile node 0.10.33, the case requires profiler to be activated in code. so --prof is not suits.</p>
  
  <p>v8tools based profilers returns profile logs in memory using json tree, which is not suits for any visualization tool.</p>
  
  <p>Main problem using node-profiler is logs received by it is not readable by any tool: nprof, chrome://tracing/ etc. For example nprof gives lots of "Code move event for unknown code" errors and </p>
  
  <pre><code> [Unknown]:
   ticks  total  nonlib   name
   146518   98.8%
  </code></pre>
  
  <p>as result.</p>
  
  <p>The same time using just --prof gives valid logs.</p>
  
  <p>As i see it node-profiler just calls to v8 built-in profiler resuming it, for thus we calls node with "--prof", "--prof_lazy", "--log" parameters. So logs must be identical.</p>
  
  <p>Where im wrong?</p>