1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
2 <html> |
2 <html> |
3 <head> |
3 <head> |
4 <meta http-equiv="content-type" |
4 <meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> |
5 content="text/html; charset=ISO-8859-1"> |
5 <title>Release Notes</title> |
6 <title>Release Notes</title> |
6 <link href="../book.css" rel="stylesheet" type="text/css"> |
7 <link href="../book.css" rel="stylesheet" type="text/css"> |
7 <style type="text/css"> |
8 <style type="text/css"> |
|
9 <!-- |
8 <!-- |
10 .style2 {font-size: 13px} |
9 .style2 {font-size: 13px} |
11 --> |
10 --> |
12 </style> |
11 |
|
12 </style> |
13 </head> |
13 </head> |
|
14 |
14 <body bgcolor="#FFFFFF"> |
15 <body bgcolor="#FFFFFF"> |
15 <h2>Performance Investigator Release Notes</h2> |
16 <h2>Release Notes</h2> |
|
17 |
|
18 <h4>Performance Investigator Analyser Carbide.c++ Extension – Version |
|
19 2.3.0</h4> |
|
20 |
|
21 <p>Released 21st April 2010</p> |
16 <ul> |
22 <ul> |
17 <li><a href="#whatsNew">What's new </a></li> |
23 <li><a href="#whatsNew">What's new </a></li> |
18 <li><a href="#agent" >Target Performance Investigator Agent</a></li> |
24 <li><a href="#agent">Target Performance Investigator Agent</a></li> |
19 <li><a href="#pi_bugs">Fixed bugs and workarounds</a></li> |
25 <li><a href="#pi_bugs">Fixed bugs and workarounds</a></li> |
20 <li><a href="#support">Technical support</a></li> |
26 <li><a href="#support">Technical support</a></li> |
21 </ul> |
27 </ul> |
|
28 |
22 <h3><a name="whatsNew" id="whatsNew"></a>What's New </h3> |
29 <h3><a name="whatsNew" id="whatsNew"></a>What's New </h3> |
23 <p>The Performance Investigator (PI) provides the means to measure program performance on a device running the Symbian OS. The new PI features provided with this release include:</p> |
30 |
24 <ul> |
31 <p><strong>2.3.0</strong></p> |
25 <li><b>Key Press profiles support</b> — PI now supports changing the key press map profile associated with a NPI file. Once changed using any of the pre-built profiles for TechView, S60, MOAP, UIQ, and PI pre-2.0, you can customize the key presses as desired to match new device functionality requirements.</li> |
32 <ul> |
26 <li><b>Performance improvements</b> — Several graphic routines have been rewritten to decrease the time it takes to draw and manipulate large data sets, making the process of changing graph sizes and scrolling them much more responsive. Also, the time to import a DAT file has been decreased. </li> |
33 <li><b>Performance improvements</b> — Improved overall memory |
27 <li><b>Memory usage improvements</b> — Memory usage has has been significantly lowered. </li> |
34 consumption. </li> |
28 </ul> |
35 <li><b>Version numbers harmonized</b> — Version numbers of Performance |
29 <p><b>1.3.1</b></p> |
36 Investigator plug-ins and feature increased to 2.3.0.</li> |
30 <ul> |
37 <li><b>Instruction trace (ITT) support</b> — Support for the RVCT 4.0 |
31 <li><b>Copy tables and paste into spreadsheets</b> — copy displayed information in Threads, Binaries, Functions, and Function Calls tables to the clipboard and paste into a spreadsheet application, such as Microsoft Excel</li> |
38 map file format.</li> |
32 <li><b>Save tables</b> — save information displayed in tables into a comma delimited .csv file format that can be opened in a spreadsheet application</li> |
39 <li><b>Library event support</b> — Memory plug-in supports |
33 <li><strong>Save more precise data in tables</strong> — save specific information about selected data within a table. For example, save samples for Threads that are checked in the Thread table or save the priority setting for Threads that are checked. You can also save data for one or more selected binaries, checked functions in Functions table, a single selected function in Function Calls table, checked memory samples, all button events for specified time interval, and all Power samples for time interval.</li> |
40 investigating memory usage by a library from the application developer's |
34 </ul> |
41 point of view. </li> |
35 <p><b>1.5.0</b></p> |
42 <li><b>Performance Investigator Import Wizard</b> — Support for |
36 <ul> |
43 importing multiple profiler data files with the same configuration from a |
37 <li><b>PI Profiler 2.02 support added.</b> — Support for more detailed event based memory model added.</li> |
44 file system, and a new possibility to select the desired views from the |
38 <li><b>Touch Event support</b> — Button plug-in is now able to recognize touch events.</li> |
45 available trace types for each imported file. </li> |
39 <li><b>Some minor usability improvements and bug fixes</b></li> |
46 </ul> |
40 </ul> |
47 |
41 <h3><a name="agent"></a>Target Performance Investigator Profiler </h3> |
48 <h3><a name="agent"></a>Target Performance Investigator Profiler </h3> |
42 <ul> |
49 <ul> |
43 <li>To produce a Profiler data file, you need to install one of these profiler agents: |
50 <li>To produce a Profiler data file, you need to install one of these |
|
51 profiler agents: |
44 <ul> |
52 <ul> |
45 <li><span class="code">Carbide Profiler 2.0 Installer</span> - for S60 3.0 (3rd Edition, initial release) devices</li> |
53 <li><span class="code">Carbide Profiler 2.0 Installer</span> - for S60 |
46 <li><span class="code">Carbide Profiler 2.0 (Dual CPU) Installer </span>- for S60 3.1 (3rd Edition, Feature Pack 1) devices with dual CPUs, such as the N95 and N96</li> |
54 3.0 (3rd Edition, initial release) devices</li> |
47 <li><span class="code">Carbide Profiler 2.0 (Single CPU)Installer</span> - for S60 3.1 (3rd Edition, Feature Pack 1) devices with a single CPU, such as the E71, N76, 6290, N78 and 5320 |
55 <li><span class="code">Carbide Profiler 2.0 (Dual CPU) Installer </span>- |
|
56 for S60 3.1 (3rd Edition, Feature Pack 1) devices with dual CPUs, such |
|
57 as the N95 and N96</li> |
|
58 <li><span class="code">Carbide Profiler 2.0 (Single CPU)Installer</span> |
|
59 - for S60 3.1 (3rd Edition, Feature Pack 1) devices with a single CPU, |
|
60 such as the E71, N76, 6290, N78 and 5320 </li> |
48 </ul> |
61 </ul> |
49 <p>Those files and others can be can be downloaded and installed using the <b>On-Device Connections > New Connection Wizard ></b><a href="PLUGINS_ROOT/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_connection_wizard.htm"> Install remote agents</a> pane.</p> |
62 <p>Those files and others can be can be downloaded and installed using the |
|
63 <b>On-Device Connections > New Connection Wizard ></b><a |
|
64 href="PLUGINS_ROOT/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_connection_wizard.htm">Install |
|
65 remote agents</a> pane.</p> |
50 </li> |
66 </li> |
51 </ul> |
67 </ul> |
|
68 |
52 <h3><a name="pi_bugs"></a>Fixed bugs and workarounds</h3> |
69 <h3><a name="pi_bugs"></a>Fixed bugs and workarounds</h3> |
53 <ul> |
70 <ul> |
54 <li>Complete list of Carbide.c++ <a href="bugs_fixed.htm">bugs fixed</a></li> |
71 <li>Complete list of Carbide.c++ <a href="bugs_fixed.htm">bugs fixed</a></li> |
55 <li>Workarounds for known issues:</li> |
72 <li>Workarounds for known issues:</li> |
56 </ul> |
73 </ul> |
57 <table width="100%" border="0" cellpadding="2" cellspacing="0" > |
74 |
58 <tr> |
75 <table width="100%" border="0" cellpadding="2" cellspacing="0"> |
59 <th width="27%" scope="col">Item</th> |
76 <tbody> |
60 <th width="62%" scope="col">Explanation</th> |
77 <tr> |
61 </tr> |
78 <th width="27%" scope="col">Item</th> |
62 <tr> |
79 <th width="62%" scope="col">Explanation</th> |
63 <td style="vertical-align: top;"><span class="style2">The Investigator menu item does not appear on the menu toolbar after an invalid format error occurs while opening an NPI file.</span></td> |
80 </tr> |
64 <td style="vertical-align: top;"><p>Workaround: To show the Investigator menu item, give focus to any non-NPI file or to any view other than the editor view (e.g., to the Symbian Project Navigator view).</p> |
81 <tr> |
65 </td> |
82 <td style="vertical-align: top;"><span class="style2">The Investigator |
66 </tr> |
83 menu item does not appear on the menu toolbar after an invalid format |
67 <tr> |
84 error occurs while opening an NPI file.</span></td> |
68 <td style="vertical-align: top;"><p>[3005] Profiling an application with all traces enabled and using the maximum sample rates (50ms and 250ms) may cause Profiler to exhibit strange behaviors</p></td> |
85 <td style="vertical-align: top;"><p>Workaround: To show the Investigator |
69 <td style="vertical-align: top;"><p>Symptoms:</p> |
86 menu item, give focus to any non-NPI file or to any view other than the |
|
87 editor view (e.g., to the Symbian Project Navigator view).</p> |
|
88 </td> |
|
89 </tr> |
|
90 <tr> |
|
91 <td style="vertical-align: top;"><p>[3005] Profiling an application with |
|
92 all traces enabled and using the maximum sample rates (50ms and 250ms) |
|
93 may cause Profiler to exhibit strange behaviors</p> |
|
94 </td> |
|
95 <td style="vertical-align: top;"><p>Symptoms:</p> |
70 <ul> |
96 <ul> |
71 <li>S60 - You may get unusual errors such loss of icons in lists.</li> |
97 <li>S60 - You may get unusual errors such loss of icons in lists.</li> |
72 <li>UIQ 3.0 - The generated .dat file is corrupted and when imported into the Analyzer can cause a crash.</li> |
98 <li>UIQ 3.0 - The generated .dat file is corrupted and when imported |
|
99 into the Analyzer can cause a crash.</li> |
73 </ul> |
100 </ul> |
74 <p>Workaround: Do not use maximum sampling rates, if all traces must be enabled, to avoid a high CPU overload condition. You can do this by either upping the time interval to 100ms/500ms or by disabling some traces.</p></td> |
101 |
75 </tr> |
102 <p>Workaround: Do not use maximum sampling rates, if all traces must be |
76 <tr > |
103 enabled, to avoid a high CPU overload condition. You can do this by |
77 <td valign="top">[3049] Profiler sampling application closes when power usage sampling is requested on a device without power management</td> |
104 either upping the time interval to 100ms/500ms or by disabling some |
78 <td valign="top"><p >On devices, such the N93, that do not have power management hardware, attempting to sample power usage will fail, and the application that samples, CProfApp, will close. </p> |
105 traces.</p> |
79 <p >There is no workaround.</p></td> |
106 </td> |
80 </tr> |
107 </tr> |
81 <tr> |
108 <tr> |
82 <td style="vertical-align: top;">Carbide.c++ may run out of memory If you open or import several large profiler data files, the Java Virtual Machine may run out of memory.</td> |
109 <td valign="top">[3049] Profiler sampling application closes when power |
83 <td style="vertical-align: top;"><p>The workaround is to allocate more memory in the Carbide.c++.ini file (typically in the Carbide.c++ folder that contains Carbide.c++.exe). For example, to allocate 1GB, edit the Carbide.c++.ini to contain “-Xmx1024m” and then restart Carbide.c++.</p> |
110 usage sampling is requested on a device without power management</td> |
84 <p class="note"><b>NOTE</b> The eclipse.ini file was renamed Carbide.c++.ini for purposes of this product.</p></td> |
111 <td valign="top"><p>On devices, such the N93, that do not have power |
85 </tr> |
112 management hardware, attempting to sample power usage will fail, and |
86 <tr> |
113 the application that samples, CProfApp, will close. </p> |
87 <td style="vertical-align: top;">Host cannot import debug output from the target device You can send sampling data to the debug port of your device. However, this release cannot import the .base64 file that contains this data.</td> |
114 |
88 <td style="vertical-align: top;">No workaround. </td> |
115 <p>There is no workaround.</p> |
89 </tr> |
116 </td> |
|
117 </tr> |
|
118 <tr> |
|
119 <td style="vertical-align: top;">Carbide.c++ may run out of memory If you |
|
120 open or import several large profiler data files, the Java Virtual |
|
121 Machine may run out of memory.</td> |
|
122 <td style="vertical-align: top;"><p>The workaround is to allocate more |
|
123 memory in the Carbide.c++.ini file (typically in the Carbide.c++ folder |
|
124 that contains Carbide.c++.exe). For example, to allocate 1GB, edit the |
|
125 Carbide.c++.ini to contain “-Xmx1024m” and then restart |
|
126 Carbide.c++.</p> |
|
127 |
|
128 <p class="note"><b>NOTE</b> The eclipse.ini file was renamed |
|
129 Carbide.c++.ini for purposes of this product.</p> |
|
130 </td> |
|
131 </tr> |
|
132 <tr> |
|
133 <td style="vertical-align: top;">Host cannot import debug output from the |
|
134 target device You can send sampling data to the debug port of your |
|
135 device. However, this release cannot import the .base64 file that |
|
136 contains this data.</td> |
|
137 <td style="vertical-align: top;">No workaround. </td> |
|
138 </tr> |
|
139 </tbody> |
90 </table> |
140 </table> |
|
141 |
91 <h3><a name="support" id="support"></a>Technical support </h3> |
142 <h3><a name="support" id="support"></a>Technical support </h3> |
|
143 |
92 <p>The following support services are available:</p> |
144 <p>The following support services are available:</p> |
93 <ul> |
145 <ul> |
94 <li>Licensed technical support - submit service requests at <a href="https://pro.forum.nokia.com/loadServiceRequest.do">Forum Nokia Developer Programs</a> (<i>not available for Express users</i>) </li> |
146 <li>Licensed technical support - submit service requests at <a |
95 <li>License issues - send questions to <a href="mailto:license.carbide@nokia.com">license.carbide@nokia.com</a> to resolve any licensing issues </li> |
147 href="https://pro.forum.nokia.com/loadServiceRequest.do">Forum Nokia |
96 <li>Visit the <a href="http://discussion.forum.nokia.com/forum/forumdisplay.php?s=&forumid=95">Forum Nokia Developer Discussion Board</a> for lively Carbide.c++ discussions </li> |
148 Developer Programs</a> (<i>not available for Express users</i>) </li> |
97 <li>Forum Nokia Wiki - visit <a href="http://wiki.forum.nokia.com/index.php/Carbide.c++">wiki.forum.nokia.com/index.php/Carbide.c++</a> for updated information, downloads and tips </li> |
149 <li>License issues - send questions to <a |
98 <li>Customer feedback - send your comments and suggestions to <a href="mailto:feedback.carbide@nokia.com">feedback.carbide@nokia.com</a></li> |
150 href="mailto:license.carbide@nokia.com">license.carbide@nokia.com</a> to |
99 </ul> |
151 resolve any licensing issues </li> |
100 <div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div> |
152 <li>Visit the <a |
101 |
153 href="http://discussion.forum.nokia.com/forum/forumdisplay.php?s=&forumid=95">Forum |
|
154 Nokia Developer Discussion Board</a> for lively Carbide.c++ discussions |
|
155 </li> |
|
156 <li>Forum Nokia Wiki - visit <a |
|
157 href="http://wiki.forum.nokia.com/index.php/Carbide.c++">wiki.forum.nokia.com/index.php/Carbide.c++</a> |
|
158 for updated information, downloads and tips </li> |
|
159 <li>Customer feedback - send your comments and suggestions to <a |
|
160 href="mailto:feedback.carbide@nokia.com">feedback.carbide@nokia.com</a></li> |
|
161 </ul> |
|
162 |
|
163 <h3>Version history</h3> |
|
164 |
|
165 <p><strong>2.2.0</strong></p> |
|
166 <ul> |
|
167 <li><b>Interrupt support</b> — Support for viewing software and |
|
168 hardware interrupts. Interrupts view can be used for tracking down low |
|
169 level performance issues.</li> |
|
170 <li><b>Performance counter support</b> — Support for viewing |
|
171 performance counter traces. This feature has been ported from Bappea to |
|
172 Performance Investigator. If the <strong>Instructions executed</strong> |
|
173 counter (performance counter number 7) has been activated during the |
|
174 profiling, the MIPS graph can be included in the Performance counter |
|
175 view.</li> |
|
176 <li><b>Interconnect performance counter support</b> — Support for |
|
177 viewing interconnect performance counter traces. This feature has been |
|
178 ported from Bappea to Performance Investigator.</li> |
|
179 <li><b>SMP support for CPU Profiler</b> — The Threads view can now be |
|
180 broken down into separate graphs, one per available CPU on SMP systems.</li> |
|
181 <li><b>Usability enhancements for graphs</b> — Title bar added for each |
|
182 graph for manipulating the location and size of a single graph.</li> |
|
183 <li><b>Version numbers harmonized</b> — Version numbers of Performance |
|
184 Investigator plug-ins and feature increased to 2.2.0.</li> |
|
185 <li><b>Instruction trace (ITT) support</b> — Support for event based |
|
186 ITT traces (ITT_V2.00).</li> |
|
187 </ul> |
|
188 |
|
189 <p><strong>1.5.0</strong></p> |
|
190 <ul> |
|
191 <li><b>PI Profiler 2.02 support added.</b> — Support for more detailed |
|
192 event based memory model added.</li> |
|
193 <li><b>Touch Event support</b> — Button plug-in is now able to |
|
194 recognize touch events.</li> |
|
195 <li>Some minor usability improvements and bug fixes</li> |
|
196 </ul> |
|
197 |
|
198 <p><b>1.3.1</b></p> |
|
199 <ul> |
|
200 <li><b>Copy tables and paste into spreadsheets</b> — copy displayed |
|
201 information in Threads, Binaries, Functions, and Function Calls tables to |
|
202 the clipboard and paste into a spreadsheet application, such as Microsoft |
|
203 Excel</li> |
|
204 <li><b>Save tables</b> — save information displayed in tables into a |
|
205 comma delimited .csv file format that can be opened in a spreadsheet |
|
206 application</li> |
|
207 <li><strong>Save more precise data in tables</strong> — save specific |
|
208 information about selected data within a table. For example, save samples |
|
209 for Threads that are checked in the Thread table or save the priority |
|
210 setting for Threads that are checked. You can also save data for one or |
|
211 more selected binaries, checked functions in Functions table, a single |
|
212 selected function in Function Calls table, checked memory samples, all |
|
213 button events for specified time interval, and all Power samples for time |
|
214 interval.</li> |
|
215 </ul> |
|
216 |
|
217 <div id="footer"> |
|
218 Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights |
|
219 reserved. <br> |
|
220 License: <a |
|
221 href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div> |
102 </body> |
222 </body> |
103 </html> |
223 </html> |