On Friday 02 November 2007, [EMAIL PROTECTED] wrote: > Author: njn > +// - Massif out file: > +// default --> cachegrind.out.<pid> > +// --cg-out-file=X --> X.<pid> > +// --cg-out-file-exactly=X --> X > +// --cg-out-file-qualifier=QUAL --> [error] > +// --cg-out-file=X --cg-out-file-qualifier=QUAL --> X.$QUAL > +// - Likewise for Cachegrind, but with --cg-out/cg.out. > +// - And in cg_annotate, remove the --<pid> option. > +// - Likewise for Callgrind, but with --cl-out/cl.out (?) > +// - And don't create .1, .2 etc suffixed files.
Hi Nick, cool, that you want to solve this mess in a consistent way. I am all for it. I am just not sure if the above is flexible enough. Eg. in callgrind, I can have output triggered from different threads, as well as multiple outputs. I think that allowing for a format pattern would be a good way. In this format pattern, we could allow for sequences to be substituted: %p <pid> of running process %t <thread> producing this output %T tool name %c counter to be incremented on each output I do not understand the benefit of QUAL above. Do I understand correctly, and you specify the name of an environment variable here that is substituted in the file name? Why can you not just say --cg-out-file=X.$QUAL (ie. the substitution is done by the shell at exec time)? With %T, we could generalize the options among the tools, e.g. by just using "--out-file=<pattern>". However. This does not really work for callgrind :-( To get the current behavior of callgrind, there is the need for four (!) such patterns for different contexts: 1) termination without separate counters per thread: %T.out.%p 2) termination with separate counters per thread: %T.out.%p-%t 3) dumping in the middle without seperate c.p.t. : %T.out.%p.%c 4) " with " : %T.out.%p.%c-%t I am open for any suggestions to unify this mess into just one pattern. The bad thing is that KCachegrind depends on this to some extend: When running KCachegrind on the generated output from termination, it searches for any further outputs with suffixes. However, I want to get rid of this because it is quite a confusing behavior. Josef ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
