> > I can see that you would want to instrument some functions and not > others, eg, FOO but not BAR. But why do you care about knowing > if some block is the entry point for a function or not?
In fact, I don't. :) > > So there's probably some function you can call in the tool-visible > interface to m_debuginfo (that is, in include/pub_tool_debuginfo.h) > to find out the name of a function containing a given code address. > VG_(get_fnname), it looks like. Cool! > I assume you will ask for the containing > function name and then not instrument it according to some criteria. Right? Right. Most likely I will just have a command line with a list of C++ functions and namespaces to skip. > Uh, that's a bit dangerous because the JIT will create superblocks > which go across function calls. Eg if BAR calls XYZZY then there > can be a block starting in BAR and ending in XYZZY, and if you > say that BAR is not to be instrumented, then you also miss > instrumentation for the part of the block in XYZZY. No problem, you > just need to disable superblock formation. Put this in the post_clo_init > function: > > VG_(clo_vex_control).guest_chase_thresh = 0; What is the expected slowdown from limiting superblocks to one BB? --kcc ------------------------------------------------------------------------- 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
