|
From: <sv...@va...> - 2008-10-30 02:41:22
|
Author: njn Date: 2008-10-30 02:41:13 +0000 (Thu, 30 Oct 2008) New Revision: 8717 Log: A clarification. Modified: trunk/cachegrind/docs/cg-manual.xml Modified: trunk/cachegrind/docs/cg-manual.xml =================================================================== --- trunk/cachegrind/docs/cg-manual.xml 2008-10-30 01:44:03 UTC (rev 8716) +++ trunk/cachegrind/docs/cg-manual.xml 2008-10-30 02:41:13 UTC (rev 8717) @@ -807,17 +807,13 @@ instructions.</para> <para>To do this, you just need to assemble your -<computeroutput>.s</computeroutput> files with assembler-level -debug information. gcc doesn't do this, but you can use the GNU -assembler with the <computeroutput>--gstabs</computeroutput> -option to generate object files with this information, eg:</para> +<computeroutput>.s</computeroutput> files with assembly-level debug +information. You can use <computeroutput>gcc +-S</computeroutput> to compile C/C++ programs to assembly code, and then +<computeroutput>gcc -g</computeroutput> on the assembly code files to +achieve this. You can then profile and annotate the assembly code source +files in the same way as C/C++ source files.</para> -<programlisting><![CDATA[ -as --gstabs foo.s]]></programlisting> - -<para>You can then profile and annotate source files in the same -way as for C/C++ programs.</para> - </sect2> <sect2 id="ms-manual.forkingprograms" xreflabel="Forking Programs"> |