|
From: Josef W. <Jos...@gm...> - 2005-05-12 15:35:32
|
On Thursday 12 May 2005 16:46, Nicholas Nethercote wrote: > On Thu, 12 May 2005, Josef Weidendorfer wrote: > > But perhaps it is best to call it CG-format (for cachegrind or > > callgrind), and thus call the converter "op2cg". > > I'd call it the "callgrind format". Cachegrind's cg_annotate script > cannot read that format, so it seems useful to preserve the distinction > between "cachegrind format" and "callgrind format". OK. Yes, makes sense. Have you ever tought about using Cachegrind's format for Massif for consensus points? I.e. event names: "Number of user bytes allocated", "Number of red zone bytes allocated", "Number of bytes freed", I know that the relation should be to call chains, not simple source positions. Callgrind can relate events to call chains, too, and uses a concatenation of the function names in the chain (seperated by an apostrophe) for the output. Hmm... as cg_annotate would have to know about this, the separation char should be part of the format. Josef > But I guess it's up > to you, Josef. > > N > > > ------------------------------------------------------- > This SF.Net email is sponsored by Oracle Space Sweepstakes > Want to be the first software developer in space? > Enter now for the Oracle Space Sweepstakes! > http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |