At work, we encountered 'not enough memory' crashes of our big application under valgrind due to the way the superblocks are managed (see bug http://bugs.kde.org/show_bug.cgi?id=250101 (there is a proposed patch to solve this bug)
However, in your case, not being able to even allocate about 20 Mb ((14.3Mb + 4.2 Mb) looks really strange : >==10577== >==10577== Valgrind's memory management: out of memory: >==10577== newSuperblock's request for 4194304 bytes failed. >==10577== 14356480 bytes have already been allocated. >==10577== Valgrind cannot continue. Sorry. So, it is unclear what is happening. Maybe the best is to enable the debug traces of valgrind to have more details. If still not clear, strace of valgrind might give even more details about the system calls leading to the above failure. 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. ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
