Am 27.06.2012 17:25, schrieb Christoph Bartoschek: > Hi, > > the manual does not explain all interactions between data collection and > instrumentation. > > I start with --instr-atstart=no > > When I then enable instrumentation with > > CALLGRIND_START_INSTRUMENTATION > > is collection activated?
The instrumentation and collection *states* are handled completely independently. However, the instrumentation state of course influences the result. If no simulation is not done, no events are triggered which could be collected. The default for the collection state is "on". Thus, in your scenario, after the macro, events will be collected. Hmm. Probably it's worth to put this into the manual. Cheers, Josef > > Thanks > Christoph > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Valgrind-users mailing list > Valgrind-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/valgrind-users > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users