|
From: Yeshurun, M. <mei...@in...> - 2005-07-21 12:52:12
|
I had the same problem. It's no big deal, I kept multiplying by 10 until it worked. I also had to increase another constant - the number of segments (#defined near VG_N_SEGNAMES, don't remember the exact name). Perhaps these constants should be increased in the released version. Regards, Meir -----Original Message----- From: val...@li... [mailto:val...@li...] On Behalf Of Christoph Bartoschek Sent: Thursday, July 21, 2005 3:33 PM To: val...@li... Subject: [Valgrind-users] AMD64 and memory Hi, Someone mentioned that with --enable-pie one can use more memory on AMD64=20 than 1.5GB. Is this correct? However I tried this and it goes further thant without --enable-pie and uses=20 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=20 other constants in this file? Christoph ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. = http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclick _______________________________________________ Valgrind-users mailing list Val...@li... https://lists.sourceforge.net/lists/listinfo/valgrind-users |