On Thu, 2013-10-31 at 21:31 +0330, hamid alaei wrote: > ----------------------------------------------------------------------- > 3- Reply to Philippe: > > ----------------------------------------------------------------------- > Thanks Philippe, > > I know that can be an interesting extension. I also hope that to > Valgrind developers doing so can be easy. For dynamically allocated > structs, I just expected a tool that can detect if the size of a hole > block/struct is large enough, not specifically one of its static array > fields. I think that work well in many cases. However, there should be > a way to implement such a runtime type checking as well: it will be > easy in the case of using new operator in C++. With malloc as well the > desired tool can guess the type of block by observing the type of > pointers in which the address of the block is stored after malloc. "observing the type of pointers ..." is what I think is complex/unclear how to do. > > > But the question here is how we can ask valgrind developers to kindly > implement such an extension. It will be very hard to me to do so and I > hope no one force me to do that!!! At least for the easy cases, that would be an interesting thing (not so difficult) to look at for a first hack on valgrind. Nobody will of course force you :).
Philippe ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
