> I get this behaviour on various distributions and several people > confirmed. I now wonder if there is a bug in udev or something is wrong > in valgrind? Any idea from the valgrind perspective?
Yes: the program is buggy (reads freed memory) and therefore its behaviour after that point is of course dependent on what free() does. I expect that if you link with a debugging malloc library that (eg) memset-0xAA's freed memory then you will also see it behaving differently, even when not run on Valgrind. J ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
