diff -r 14dc2103a631 -r ed1c9f64298a trace/tracebuilder/com.nokia.tracebuilder.help/html/tasks/instrumenting.htm --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/tracebuilder/com.nokia.tracebuilder.help/html/tasks/instrumenting.htm Wed Jun 23 14:35:40 2010 +0300 @@ -0,0 +1,62 @@ + + + +Instrumenting traces + + + +

Instrumenting traces

+

To instrument traces to your source code, do the following:

+
    +
  1. From the TraceBuilder menu, select Instrument Code.
  2. +
  3. Select a group for your traces or define a new one by typing the name + into the Trace Group field.
  4. +
  5. Type a name format for your traces. +

    The default is {$CN}_{$FN}, which means + className_functionName.

    +

    The values for className and functionName + are parsed from the source code.

  6. +
  7. Type a text format for your traces. +

    The default is {$cn}::{$fn}, which means + className::functionName.

    +

    The values for className and functionName + are parsed from the source code.

  8. +
  9. (Optional) From the Templates list, you can select pre-defined + format for the trace. +

    For example, Function entry-exit template parses the name + of the class and function where the cursor is currently located. + An entry trace is added to the beginning of the function and the exit trace + is added to the end.

  10. +
  11. (Optional) Select any of the following options, as needed: + +
  12. +
  13. Click OK.
  14. +
  15. In the displayed dialog, select the functions you want to instrument.
  16. +
  17. Click OK to start instrumentation of the source code.
  18. +
+ +
Related tasks
+ + +
Related concepts
+ + + + + \ No newline at end of file