Adding traces to the source code

diff -r 14dc2103a631 -r ed1c9f64298a trace/tracebuilder/com.nokia.tracebuilder.help/html/tasks/addingtraces.htm --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/tracebuilder/com.nokia.tracebuilder.help/html/tasks/addingtraces.htm Wed Jun 23 14:35:40 2010 +0300 @@ -0,0 +1,48 @@ + + + +Adding traces to the source code + + + +

Adding traces to the source code

To add a new trace, do the following:

Place the cursor in your source code where you want to add the trace.
Click the TraceBuilder menu and select Add New Trace.
In the Add Trace dialog, enter trace group, name, and text: +
- Trace Group: the trace group is needed when you want to activate + your traces from the device. There are some predefined groups which you + can use if your trace fits the purpose. You can also define your own group + just by typing to the field.
- Trace Name: the trace name is needed for creating unique identifiers + for each OST trace so that they can be identified in the PC side. + The trace name must be unique.
- Trace Text: enter here the string you want to see when you receive + the trace in TraceViewer.
- (Optional) From the Templates list, you can select pre-defined + format for the trace name and trace text. +
  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.
+
+
Click OK. You should get this kind of line to your source code:

+

+ +

The trace is added to the defined location in the code, and details +such as the trace group are displayed in TraceBuilder's tree view.

+ +

Related tasks

+ + + + \ No newline at end of file