|
From: Yuri
|
I am running --tool=callgrind on my executable, runs fine but doesn't load debug info. I debugged valgrind itself and found that VG_(find_map_space) called from VG_(mmap) returns null and further analysis and enabling of printout showed that executable with debug info is loaded into [valgrind_base - valgrind_end] space and memory limits are: client_base 0 (937MB) client_mapbase 3A965000 (1877MB) client_end AFF00000 (1MB) shadow_base B0000000 (0MB) shadow_end B0000000 (0MB) valgrind_base B0000000 (255MB) valgrind_end BFFFFFFF and my executable is 271,272,753 bytes (with debug info). Is it a way to still load debug info for my 270 MB executable ? Thanx, Yuri |