Lines Matching full:opannotate
486 <term><filename>opannotate</filename></term>
490 debugging symbols. See <xref linkend="opannotate" />.
1371 <command>opannotate</command>, or <command>opgprof</command>.
2101 <sect1 id="opannotate">
2102 <title>Outputting annotated source (<command>opannotate</command>)</title>
2104 The <command>opannotate</command> utility generates annotated source files or assembly listings, optionally
2110 use <command>opannotate <option>--assembly</option></command> to get annotated assembly.
2131 $ opannotate --source --output-dir=annotated /usr/local/oprofile-pp/bin/oprofiled
2164 <sect2 id="opannotate-finding-source">
2167 Of course, <command>opannotate</command> needs to be able to locate the source files
2184 $ opannotate --source --base-dirs=/tmp/build/libfoo/ --search-dirs=/home/user/libfoo/ --output-dir=annotated/ /lib/libfoo.so
2191 <sect2 id="opannotate-details">
2192 <title>Usage of <command>opannotate</command></title>
2241 Output directory. This makes opannotate output one annotated file for each
2265 </sect2> <!-- opannotate-details -->
2267 </sect1> <!-- opannotate -->
2282 <command>opannotate</command>) can now be used
2307 Depending on the JVM that is used, certain options of opreport and opannotate
2532 $ opannotate -a -t 10 ./a.out
2550 $ opannotate -s -t 10 ./a.out
2678 <command>opannotate <option>-a</option></command> can help to show the real
2733 definition, and this is where <command>opannotate</command> annotates
2765 When running <command>opannotate</command>, you may get a warning
