> >The 0x10000000 stems from my experimenting around (in particular, >0x10000000 was a definitely free area in my runtime >environment); as far >as the test case is concerned, mmap should probably just be called >with NULL as first argument to pick any available address.
It does not arm to use 0x10000000 so I preferred to keep the address you had in your test case. In case this address is not free, mmap returns another one. I have tested a.o. on debian5/ppc64, in which 0x10000000 is not ok and on e.g. f12/x86, where it is ok. In both cases, the test was failing without the patch, and succeeds with the patch (whatever the address returned by the initial mmap). 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 of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
