title: How to use callgrind on Centos Linux 5.5
body: <p>I am trying to use the callgrind profiler to profile my C++ program. I am using Valgrind version 3.6,1 on Linux Centos Version 5.5 on a Intel 32-bit processor.  I keep getting the following error(shown below) when I try to profile my program.
           I already used Linux gprof but it didn't provide any useful profiling information. Please tell me what I am doing wrong or what  workaround I should use. Thank you</p>
  
  <p>valgrind --tool=callgrind --dump-instr=yes --simulate-cache-yes --collect-jumps=yes 
   ./MatchUpAccurate.exe -input /home/frankc/DQTTest5/MatchUpTest/TestData/mdata2003.dbf 
  -fileloc /home/frankc/DQTTest5/MatchUpTest/TestData -version 15, </p>
  
  <p>==25558== Callgrind, a call-graph generating cache profiler, 
  ==25558== Copyright (C) 2002-2010, and GNU GPL'd, by Josef Weidendorfer et al., 
  ==25558== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info, 
  ==25558== Command: ./MatchUpAccurate.exe -input /home/frankc/DQTTest5/MatchUpTest/TestData/mdata2003.dbf -fileloc /home/frankc/DQTTest5/MatchUpTest/TestData -version 15, 
  ==25558==, 
  ==25558== For interactive control, run 'callgrind_control -h'., 
  memcpy, 
  BB# 486126, </p>
  
  <p>Callgrind: jumps.c:164 (new_jcc): Assertion '(0 &lt;= jmp) &amp;&amp; (jmp &lt;= from->bb->cjmp_count)' failed., 
  ==25558==    at 0x3801E4C8: report_and_quit (m_libcassert.c:193), 
  ==25558==    by 0x3801E69C: vgPlain_assert_fail (m_libcassert.c:267), 
  ==25558==    by 0x3800FCD9: vgCallgrind_get_jcc (jumps.c:164), 
  ==25558==    by 0x38003534: vgCallgrind_push_call_stack (callstack.c:217), 
  ==25558==    by 0x38001FDB: vgCallgrind_setup_bbcc (bbcc.c:844), 
  ==25558==    by 0x629B9E93: ???, </p>
  
  <p>sched status:, 
      running_tid=1, </p>
  
  <p>Thread 1: status = VgTs_Runnable, 
  ==25558==    at 0xB64A30: memcpy (in /lib/libc-2.5.so), 
  ==25558==    by 0xC845D3: __pthread_initialize_minimal (in /lib/libpthread-2.5.so), 
  ==25558==    by 0xC84217: ??? (in /lib/libpthread-2.5.so), 
  ==25558==    by 0xC83DA7: ??? (in /lib/libpthread-2.5.so), 
  ==25558==    by 0xAE2162: call_init (in /lib/ld-2.5.so), 
  ==25558==    by 0xAE228F: _dl_init (in /lib/ld-2.5.so), 
  ==25558==    by 0xAD484E: ??? (in /lib/ld-2.5.so), </p>
  
  <p>Note: see also the FAQ in the source distribution., 
  It contains workarounds to several common problems., 
  In particular, if Valgrind aborted or crashed after, 
  identifying problems in your program, there's a good chance, 
  that fixing those problems will prevent Valgrind aborting or, crashing, 
  especially if it happened in m_mallocfree.c., </p>
  
  <p>If that doesn't help, please report this bug to: www.valgrind.org, </p>
  
  <p>In the bug report, send all the above text, the valgrind, 
  version, and what OS and version you are using.  Thanks.</p>