On 01/04/11 10:50, Julian Seward wrote: > > [... mucho discussion ...] > > I'm now comprehensively confused. Is there any bug/failure in > Memcheck resulting from this, that needs to be looked at?
There is no clear evidence of one at the moment. The current situation is that we have proved that the test program really did have a leak that was correctly reported. The only outstanding question there was about why memory allocation was failing under valgrind when it worked normally but that is expected. As to the original program, who knows... It was apparently reporting a read(2) into memory that was beyond an allocated block but we don't really know any more than that. Tom -- Tom Hughes ([email protected]) http://compton.nu/ ------------------------------------------------------------------------------ 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
