|
From: Christoph B. <bar...@or...> - 2005-07-21 12:34:06
|
Hi, Someone mentioned that with --enable-pie one can use more memory on AMD64 than 1.5GB. Is this correct? However I tried this and it goes further thant without --enable-pie and uses 3.5GB when it stops with the following message: coregrind/m_aspacemgr/aspacemgr.c: VG_N_SEGNAMES is too small: increase it and rebuild Valgrind. coregrind/m_aspacemgr/aspacemgr.c: giving up now. What would be a reasonable value for this constant? Should I also increase the other constants in this file? Christoph |
|
From: Julian S. <js...@ac...> - 2005-07-21 12:39:03
|
> coregrind/m_aspacemgr/aspacemgr.c: > VG_N_SEGNAMES is too small: increase it and rebuild Valgrind. > coregrind/m_aspacemgr/aspacemgr.c: > giving up now. > > What would be a reasonable value for this constant? Should I also increase > the other constants in this file? Just keep doubling it until it works, then let me know what you had to set it to. J |
|
From: Christoph B. <bar...@or...> - 2005-07-21 14:38:23
|
Am Donnerstag 21 Juli 2005 14:39 schrieb Julian Seward: > > coregrind/m_aspacemgr/aspacemgr.c: > > VG_N_SEGNAMES is too small: increase it and rebuild Valgrind. > > coregrind/m_aspacemgr/aspacemgr.c: > > giving up now. > > > > What would be a reasonable value for this constant? Should I also > > increase the other constants in this file? > > Just keep doubling it until it works, then let me know what you had > to set it to. 500 works, but I did not get to the end of loaded libraries because valgrind stopped: VG_(get_memory_from_mmap): newSuperblock's request for 2052096 bytes failed. VG_(get_memory_from_mmap): 242441728 bytes already allocated. Sorry. You could try using a tool that uses less memory; eg. addrcheck instead of memcheck. Christoph |