On 10/11/10 20:30, Peter Toft wrote: > With my favorite program valgrind I got a new warning today with a program > I made; > > Warning: set address range perms: large range<number> > > From the google search I understand that it comes when I malloc/new a HUGE > chunk of data (which is the case).
That may be one cause, but it's not the only one - calls to mmap, munmap and mprotect may also trigger it. > Question; > * can I adjust a valgrind-setting of how my bytes is needed before the > warning is triggered? Only by changing the source and recompiling I believe. > If I cannot adjust a level, then I need a little help with creating a > suppression rule for it - the best is of the rule can allow a certain > (controllable) number of digits. The issue is that I am allocating ~40 MB, > and it is a nice warning if I by accident asked for say 10x i.e. 400MB. There is no way to write a suppression rule for them - they aren't formal warnings issued through the main warning system where suppressions are supported. It's just an ah-hoc warning message. Mostly you can just ignore it - it has minimal value. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
