|Valgrind 3.3 - Advanced Debugging and Profiling for GNU/Linux applications|
by J. Seward, N. Nethercote, J. Weidendorfer and the Valgrind Development Team
Paperback (6"x9"), 164 pages
RRP £12.95 ($19.95)
7.4.2 Dump creation options
These options influence the name and format of the profile data files.
--callgrind-out-file=<file>Write the profile data to ‘file’ rather than to the default output file, ‘callgrind.out.<pid>’. The
%qformat specifiers can be used to embed the process ID and/or the contents of an environment variable in the name, as is the case for the core option
--log-file. See 3.6.2 for details. When multiple dumps are made, the file name is modified further; see below.
--dump-instr=<no|yes> [default: no]This specifies that event counting should be performed at per-instruction granularity. This allows for assembly code annotation. Currently the results can only be displayed by KCachegrind.
--dump-line=<no|yes> [default: yes]This specifies that event counting should be performed at source line granularity. This allows source annotation for sources which are compiled with debug information (
--compress-strings=<no|yes> [default: yes]This option influences the output format of the profile data. It specifies whether strings (file and function names) should be identified by numbers. This shrinks the file, but makes it more difficult for humans to read (which is not recommended in any case).
--compress-pos=<no|yes> [default: yes]This option influences the output format of the profile data. It specifies whether numerical positions are always specified as absolute values or are allowed to be relative to previous numbers. This shrinks the file size,
--combine-dumps=<no|yes> [default: no]When multiple profile data parts are to be generated, these parts are appended to the same output file if this option is set to “yes”. Not recommended.
|ISBN 0954612051||Valgrind 3.3 - Advanced Debugging and Profiling for GNU/Linux applications||See the print edition|