On Sat, 3 Nov 2007, Josef Weidendorfer wrote: > 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)?
It's somehow important for MPI programs, where you want every different process's output to go to a different file. I don't know the details. > 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. A format string seems like a good way to do it. But it's not obvious how to do it for Callgrind. Hmm. Nick ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
