Hi,
>From Valgrind's 3.13.0 NEWS, I see that:
* The amount of memory that Valgrind can use has been increased from 64GB to
128GB. In particular this means your application can allocate up to about
60GB when running on Memcheck.
* Valgrind's default load address has been changed from 0x3800'0000 to
0x5800'0000, so as to make it possible to load larger executables. This
should make it possible to load executables of size at least 1200MB.
But I get this error:
valgrind: mmap(0xa64000, 1793339392) failed in UME with error 22 (Invalid
argument).
valgrind: this can be caused by executables with very large text, data or bss
segments.
when trying to analyse an executable with 13 MB that occupies 2.6 GB virtual
memory (1.7 GB resident).
This program is written in Ada/SPARK and C/C++ and most of the memory (99%) is
statically allocated.
Does anyone know what's wrong?
Thanks.
João M. S. Silva
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
