|
From: Peter T. <pt...@li...> - 2010-11-10 20:49:11
|
Hi all 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). Question; * can I adjust a valgrind-setting of how my bytes is needed before the warning is triggered? 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. Best Peter Peter Toft, Ph.D. [pt...@li...] http://petertoft.dk I blog at http://www.version2.dk/blogs/petertoft |
|
From: Tom H. <to...@co...> - 2010-11-10 21:08:15
|
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 (to...@co...) http://compton.nu/ |