|
From: Rex W. <wa...@gm...> - 2005-04-24 21:52:12
|
THanks. that is all I wanted to know. I wanted to know if the same principle used in callgrind could be used for dullard. THanks again. Rex. On 4/24/05, Josef Weidendorfer <Jos...@gm...> wrote: > On Friday 22 April 2005 15:48, Rex Walburn wrote: > > Hi > > You had mentioned the macro CALLGRIND_START_INSTRUMENTATION that can > > be used to start instrumentation at a particular point in the source > > code. So can I use this same macro for another tool like "dullard" > > which dumps out memory traces for an executable ? >=20 > Sorry, no. > This macro will be ignored when run with a Valgrind tool other than callg= rind. > You would have to add similar support to Dullard. > But perhaps it would be good to generalize this for all tools: A tool wit= h > different instrumentation levels should be able to specify this to Valgri= nd > core, which will handle all the rest, i.e. flush the translation cache on= a > change. Neverless, "dullard" would have to be changed to support such an > Valgrind extension. >=20 > Josef >=20 > > > > THanks > > Rex > |