tmf: Handle spaces in function names in the Callstack View

[deliverable/tracecompass.git] / doc / org.eclipse.tracecompass.doc.user / doc / User-Guide.mediawiki

diff --git a/doc/org.eclipse.tracecompass.doc.user/doc/User-Guide.mediawiki b/doc/org.eclipse.tracecompass.doc.user/doc/User-Guide.mediawiki
index a88b27eb72fdcd9266c5d1166bbd9cf544a6f6a5..3c8597961a30a1f3254dfc26307b06ab7d315d86 100644 (file)
--- a/doc/org.eclipse.tracecompass.doc.user/doc/User-Guide.mediawiki
+++ b/doc/org.eclipse.tracecompass.doc.user/doc/User-Guide.mediawiki
@@ -1755,6 +1755,8 @@ If you followed the steps in the previous section, you should have a Callstack V
 ** <pre>nm myprogram > mapping.txt</pre>
 * Click the '''Import Mapping File''' ([[Image:images/import.gif]]) button in the Callstack View, and select the ''mapping.txt'' file that was just created.
 
+(If you are dealing with C++ executables, you may want to use ''nm --demangle'' instead to get readable function names.)
+
 The view should now update to display the function names instead. Make sure the binary used for taking the trace is the one used for this step too (otherwise, there is a good chance of the addresses not being the same).
 
 == Memory Usage ==