On Thursday 15 November 2007, Nicholas Nethercote wrote: > On Thu, 15 Nov 2007, Josef Weidendorfer wrote: > > >> Overall, we'd have a --log-file option for normal Valgrind output (ie. what > >> normally goes to stderr), and then for each tool that writes an output file > >> (Cachegrind, Callgrind, Massif) there would be an option like --massif-file. > >> In the Callgrind case it would be --callgrind-file-prefix. > > > > Do we really want the tool name in the option? I would vote for one global > > option "--output-file=..." to specify an output file name/pattern, and the tool > > is free to add suffixes. This makes it easier for the user to remember > > * the option name and > > * the fact that this option allows for pattern specification. > > An example: for Cachegrind, there is the "log output", ie. what normally is > printed to stderr, and there is the "file output", ie. what goes in > cachegrind.out.*. You need to be able to control the file names of these > two separately. So a single global options won't suffice.
The "global single option" was meant to be about the output file only. Of course there also is a log output that already can be redirected with "--log-file". But we currently do not have a per-tool option for the log output of each tool. Why do we want different options to specify the output file of each tool then? Josef > > 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
