|
From: Josef W. <Jos...@gm...> - 2009-06-09 23:05:51
|
On Tuesday 09 June 2009, Joseph Winston wrote: > Here's what happens when I run callgrind inside of gdb: > ... > (gdb) run --num-callers=50 --show-emwarns=yes --smc-check=all bin/Test1.exe You should run it in the debugger including the option "--tool=callgrind" (this needs to be added to README_DEVELOPERS), because otherwise, the preload library for memcheck will be loaded, leading to errors such as > ==16049== For interactive control, run 'callgrind_control -h'. > --16049-- VG_USERREQ__CLIENT_CALL1: func=0x0 which is bogus. > Operating system error: Success > Memory allocation failed No idea what's wrong here. As Julian said, your program seems to have a bug somewhere. Josef |