Hi, On Sunday 09 March 2008, waseem wrote: > At moment i anticipate it could be done in following two ways. > > 1). inserting some sort of macro in file myTest.C so that when ever we > encounter it we know that following function is an event.
This macro would be a Valgrind client request, as I already said before. It needs you to be comfortable with modifying the code to analyze. > 2). or some sort of functionality already provided in VALGRIND 3.3.0 (which > i failed to find out). Nothing "high level". You need to do this manually: Check at instrumentation time, if an instruction enters a given function (event1/2) by using debug info, and insert a callback into the instruction stream to call your own function which does act as needed. If you do not want to hardcode the function names into your tool, you could have a look at command line parsing in callgrind. E.g. there, "--dump-before=<func>" allows to specify a function where profiling result should be dumped before entering. Here, "<func>" can even include wildcards. Josef > > So i hope, my question is much clear now and i will appreciate all sort of > help . > > Thanking you in anticipation for your time and consideration > > With Best Regards > Waseem > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
