Am 29.10.2013 03:27, schrieb Loi Luu: > supports many useful tools. I'm thinking to use *Callgrind *to solve my > problem, but I'm not sure whether its a right choice.
Callgrind does observe branch behavior, and counts how often instructions from various branches are executed. The source annotation may already be enough for you, but it gives more details to see it at instruction level, and also see the jump behavior. For that, check out the callgrind options "--dump-instr=yes --collect-jumps=yes", and look at the machine code annotation in KCachegrind. Not sure this is really what you want. Josef Could you please > give me some suggestion? Is this a possible approach and how can I > process this way? > > Thank you, > > -- > > Loi, Luu The (Mr.) > RA at Security Lab, SoC, NUS > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
