|
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
|
2 <html> |
|
3 <head> |
|
4 <title>Viewing line count and variable tracing items</title> |
|
5 <link href="../../book.css" type="text/css" rel="stylesheet"></head> |
|
6 <body> |
|
7 |
|
8 <h2>Viewing line count and variable tracing items</h2> |
|
9 <h5>Before you start</h5> |
|
10 <p>On the <b>TraceViewerPropertyView</b>, you can check the properties |
|
11 of traces the based on the rules that were defined for line count and variable |
|
12 tracing.</p> |
|
13 <ul> |
|
14 <li><b>Line count</b> can be used to calculate the number of occurrences for |
|
15 a certain type of trace. This may mean, for example, a trace from a specific |
|
16 component, from a certain group of a certain component, or traces that contain |
|
17 a certain text. </li> |
|
18 <li><b>Variable tracing</b> means that you can follow up or monitor certain |
|
19 values that occur in traces. <p>For example, to monitor RAM consumption in |
|
20 the Kernel, there can be the following kind of trace: <br><br><i>00:11:31:624 |
|
21 [0] Kernel Memory:Initial free RAM;Bytes:127598592</i><br><br>When you create |
|
22 a variable tracing rule that contains the text <i>Kernel Memory:Initial free |
|
23 RAM;Bytes</i>, you can view what the latest value of this variable was, as |
|
24 well as a number of its previous values.</p></li> |
|
25 </ul> |
|
26 |
|
27 <p>For generic instructions on how to create rules and definitions, see |
|
28 instructions in <a href="setup_rules.htm">Setting up rules and filters</a>. |
|
29 </p> |
|
30 |
|
31 <h3><a name="varhist"></a>Viewing variable tracing history</h3> |
|
32 <p>To open the history: </p> |
|
33 <ol> |
|
34 <li>Select one or more items from the list. </li> |
|
35 <li>Right-click and select <b>Open history</b> from the menu. |
|
36 <p>The <b>Variable tracing history</b> dialog is displayed.</p> |
|
37 <p><img src="images/variabletracingHistoryDialog.png" |
|
38 alt="Variable Tracing History Dialog"></p> |
|
39 <p>In the history, you can see the last <i>n</i> number of events of |
|
40 the variable changing. There is a timestamp (and time from the previous event), |
|
41 new value and the line number where the change happened. The <b>Has codeline</b> |
|
42 column indicates whether or not this item has location metadata available.</p></li> |
|
43 <li>(Optional) To open the source code of a line that has had changes: |
|
44 <ol> |
|
45 <li>Select the <b>Activate corresponding codeline</b> box.</li> |
|
46 <li>Double-click a line that shows <b>Yes</b> in the <b>Has codeline</b> column. </li> |
|
47 </ol> |
|
48 </li> |
|
49 <li>(Optional) To view the line number where changes happened: |
|
50 <ol> |
|
51 <li>Select the <b>Activate corresponding trace</b> box, if not selected already. </li> |
|
52 <li>Double-click a line in the dialog and TraceViewer jumps to that line in the code. </li> |
|
53 </ol> |
|
54 </li> |
|
55 </ol> |
|
56 <p><b>Tip</b>: If you close TraceViewer when you have any of the variable |
|
57 tracing rules enabled, they will get automatically enabled the next time you start TraceViewer.</p> |
|
58 |
|
59 <h5>Related tasks</h5> |
|
60 <ul> |
|
61 <li><a href="setup_rules.htm">Setting up rules and filters</a></li> |
|
62 </ul> |
|
63 |
|
64 <div id="footer">Copyright © 2007-2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.</div> |
|
65 </body> |
|
66 </html> |