|
From: Yeshurun, M. <mei...@in...> - 2005-09-06 10:31:59
|
Multiply the subtracted value by 2, try running Valgrind again, and if it's not enough, try multiplying by 2 again, and so on. In general, you should use the smallest value that works. You should do the same for KICKSTART_BASE with the non-PIE build, i.e. multiply by 2 the value you're subtracting from it until it works. Use the highest value for KICKSTART_BASE that works. Regards, Meir -----Original Message----- From: val...@li... [mailto:val...@li...] On Behalf Of Christoph Bartoschek Sent: Tuesday, September 06, 2005 11:45 AM To: val...@li... Subject: Re: [Valgrind-users] newSuperblock's request for 1048576 bytes failed with valgrind 3.0.1 Am Dienstag, 6. September 2005 10:17 schrieb Yeshurun, Meir: > Hi, > > I once had this problem and Tom showed me how to solve it (hopefully it > will work in your case as well). > > When not using PIE, in the configure script, change the value of > KICKSTART_BASE to 0xA0000000 (i.e. just change the 'B' to 'A') for the > relevant platform, and configure,make,make install again. > > When you are using PIE, the way to do the same thing is to increase the > value subtraced from exe_end to compute exe_base in line 272 of > coregrind/stage1.c Thanks, what is a suggested value for subtracting from exe_end in the PIE=20 case? Christoph ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Valgrind-users mailing list Val...@li... https://lists.sourceforge.net/lists/listinfo/valgrind-users |