On 04/01/2011 08:32 AM, WAROQUIERS Philippe wrote: > I suggest to look at two "fixes/improvements": > 1. integrate the patch https://bugs.kde.org/show_bug.cgi?id=250101 > (I just tried a 3.7.0 SVN with this (updated) patch, and > the program of Bob Harris works now perfectly till the end, > without leaks/without out of memory).
I have voted +10 for this patch. [Why did it not appear in 3.6.x?] > > 2. add a new kind of error in memcheck: "failed (re-)allocation". > It is quite frequent to see code which forgets to check the > return of malloc/realloc. Memcheck can then at least detect > and report specifically when it has really failed. > Now, a failed client (re-)alloc is invisible, and makes a lot of > people lose a lot of time to re-discover the problem. I support such a warning the first time (each) for malloc and realloc. For realloc because memcheck tries to increase the chances of such an error; for malloc because of general cleanliness. I'm wary of giving a warning every time: too much noise for good programs which correctly check and recover, but that happen to run out of space. -- ------------------------------------------------------------------------------ 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
