|
From: Julian S. <js...@ac...> - 2011-03-26 06:58:07
|
> 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 |