>> I understand the worry, but at least in my experience, I have not seen >> much programs which effectively go to an out of memory situation and >> then check and recover. > >I'd say it's the other way around: most programs already check. ... >Calls to malloc from third-party libraries are covered by interposing >using LD_PRELOAD and RTLD_NEXT. (I admit that effective _recovery_ >from 0==malloc() is almost non-existent.) I think we both say the same, i.e. "programs that check **and** recover" is very unfrequent. Taking that into account, I think that handling a failed (re-)alloc like any other Valgrind error (i.e. reporting each occurences) will not cause much disturbances.
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. ------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
