|
From: Juan D. H. <ju...@ya...> - 2008-10-23 13:11:40
|
Thanks a lot, I found the problem, there were some enormous statically-allocated arrays !!
Now, I allocate those arrays on startup; those arrays are used for a hash table that contains the pointers, another solution was to create them with smaller size.
Juan David
________________________________
From: Nicholas Nethercote <nj...@cs...>
To: Juan David Hernandez <ju...@ya...>
Cc: val...@li...
Sent: Thursday, October 23, 2008 2:43:03 AM
Subject: Re: [Valgrind-users] valgrind: mmap(0x8054000, 1006632960) failed in UME with error 22 (Invalid argument).
On Wed, 22 Oct 2008, Juan David Hernandez wrote:
> I am a new user of valgrind.
> I'm using a matrix/vector library, meschach, it uses static variables. I'm extending that library, to have some new data types. I tried to debug the memory to find possible leaks; unfortunately, when I run valgrind I got this error:
>
> valgrind: mmap(0x8054000, 1006632960) failed in UME with error 22 (Invalid argument).
> valgrind: this can be caused by executables with very large text, data or bss segments.
>
> Does anybody know the reason? Is there any solution?
> Thanks for any help.
I guess you've got an enormous statically-allocated array somewhere. If you
can take it out and instead allocate it on startup with malloc, you'll have
a much better chance.
Nick
|