In fact, it is trivial to go over 32GB (including for the freelist
volume).
Here are the changes:
In memcheck/mc_main.c, insert '10*' to obtain:
else if VG_BINT_CLO(arg, "--freelist-vol", MC_(clo_freelist_vol),
0,
10*10*1000*1000*1000LL) {}
in coregrind/m_aspacemgr/aspacemgr-linux.c, insert a '0' to obtain:
#define VG_N_SEGMENTS 50000
And change the below line to obtain what you want for max address space
(e.g. 64G):
1652c1652
< aspacem_maxAddr = (Addr)0x800000000 - 1; // 32G
---
> aspacem_maxAddr = (Addr)((2 * 0x800000000) - 1); // 64G
Note that I understood memcheck will become (a lot?) slower when going
over 32GB.
Philippe
____
This message and any files transmitted with it are legally privileged and
intended for the sole use of the individual(s) or entity to whom they are
addressed. If you are not the intended recipient, please notify the sender by
reply and delete the message and any attachments from your system. Any
unauthorised use or disclosure of the content of this message is strictly
prohibited and may be unlawful.
Nothing in this e-mail message amounts to a contractual or legal commitment on
the part of EUROCONTROL, unless it is confirmed by appropriately signed hard
copy.
Any views expressed in this message are those of the sender.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
