aboutsummaryrefslogtreecommitdiff
path: root/cachegrind/docs/cg-manual.xml
diff options
context:
space:
mode:
authornjn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9>2008-10-30 02:41:13 +0000
committernjn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9>2008-10-30 02:41:13 +0000
commit85a38bc73d51f1d02ce2f6ea1fe058ac4e3cdfb5 (patch)
tree16b90c1d52892aa7061aa533136e34f880f2a89e /cachegrind/docs/cg-manual.xml
parent7d7691194ba0f1011b341ccc517f8a474169f403 (diff)
downloadvalgrind-85a38bc73d51f1d02ce2f6ea1fe058ac4e3cdfb5.tar.gz
A clarification.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8717 a5019735-40e9-0310-863c-91ae7b9d1cf9
Diffstat (limited to 'cachegrind/docs/cg-manual.xml')
-rw-r--r--cachegrind/docs/cg-manual.xml16
1 files changed, 6 insertions, 10 deletions
diff --git a/cachegrind/docs/cg-manual.xml b/cachegrind/docs/cg-manual.xml
index 7c1764e00..f65272bbc 100644
--- a/cachegrind/docs/cg-manual.xml
+++ b/cachegrind/docs/cg-manual.xml
@@ -807,16 +807,12 @@ interesting line of C code is translated into multiple
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>
-
-<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>
+<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>
</sect2>