title: Valgrind's massif tool will not profile my application
body: <p>I am developing a statically-linked 64-bit C++ application on 64-bit CentOS 5.8 using the standard gcc 4.4 packages from the CentOS repositories. It appears to be using more memory than I expected, so I tried using massif to profile the memory usage. I have compiled with debug information and then run </p>
  
  <blockquote>
    <p>valgrind --tool=massif ./MyProg</p>
  </blockquote>
  
  <p>from the directory where MyProg resides. It never produces any results other than the following massif.out.XXXX example.</p>
  
  <pre><code>desc: (none)
  cmd: ./MyProg
  time_unit: i
  #-----------
  snapshot=0
  #-----------
  time=0
  mem_heap_B=0
  mem_heap_extra_B=0
  mem_stacks_B=0
  heap_tree=empty
  </code></pre>
  
  <p>Note that that is the entire contents of the file and my program can run for many minutes.</p>
  
  <p>I have tried various options to valgrind and massif to no avail. I even tried using the absolute path to MyProg, just in case. I've tried downloading the most recent stable version of valgrind (3.8.1) and compiling and running that (since CentOS is using 3.5.0) with the same result. As a sanity check I ran</p>
  
  <blockquote>
    <p>valgrind --tool=massif ls -l</p>
  </blockquote>
  
  <p>and it produced multiple snapshots with non-zero memory usage as expected.</p>
  
  <p>I've tried searching online using every combination of keywords I could think of but did not find any similar problems.</p>
  
  <p>As a side note, I can successfully profile the application using valgrind's default memcheck tool, in case that is useful information.</p>
  
  <p>Does anyone know why massif would fail to profile my application?</p>