|
From: Nicholas N. <nj...@ca...> - 2004-08-05 12:26:43
|
On Thu, 5 Aug 2004, pkr wrote: > 2 pieces of info. > 1. As Nick guessed earlier, the kernel is configured for 4GB and 2GBuser/2GB > kernel . > > Let me know if there could be a fix from valgrind. Try this: - in coregrind/stage1.c, change "info.mapbase" on line 181 from 0xb1000000 to 0x71000000. - in coregrind/Makefile, change "kickstart_base" from 0xb0000000 to 0x70000000. - re-make Valgrind I found that Memcheck and Helgrind do not work under this setup, because they cannot load libraries at 0x40000000 as they want to -- the tools reserve too much of the 2GB address space for themselves. However, Addrcheck, Cachegrind and Massif do work, as they need less space for themselves, which is a start. Note that if you try running big programs under Valgrind, you might run out of memory, as the system doesn't have that much to play with. It really would be nice to improve on this situation. N |