Profiling and logging tools - release notes

Profiling and logging tools component release notes

1.0 Limitations
   1.1 How to open the Console view in the Profiling and Logging perspective
   1.2 Tips while profiling your application.
2.0 Known problems
   2.1 Probekit: Do not use non-ASCII characters in Probekit source file names
   2.2 Probekit: Non-ASCII characters in Probekit Target specifications
   2.3 Double byte characters do not show up in console view

Profiling and logging tools component release notes

1.0 Limitations

1.1 How to open the Console view in the Profiling and Logging perspective

When you profile an application, the console view does not appear in the Profiling and Logging perspective by default.

To open the console view in the Profiling and Logging perspective, select Window->Show View->Console.

To get stdout to appear in the Console click Window->Preferences->Run/Debug->Console and select Show when program writes to standard out.

1.2 Tips while profiling your application.

The performance of the profiling tools is directly related to the amount of data being collected, and the rate at which this data is transferred to the workbench. As the amount of data being collected increases, a user will experience decreased performance both in terms of the time it takes to do analysis, and in terms of the memory available for performing different tasks. There are several ways that a user can enhance the profiling performance.

2.0 Known problems

2.1 Probekit: Do not use non-ASCII characters in Probekit source file names

Probekit source files with non-ASCII characters in their names will not be processed correctly. Use only ASCII characters in Probekit source file names.

2.2 Probekit: Non-ASCII characters in Probekit Target specifications

Do not use non-ASCII characters in the patterns for Probekit "Target" specifications. Probes which contain non-ASCII characters in Target patterns will not be processed correctly.

2.3 Double byte characters do not show up in console view

During profiling, all double byte characters show up as ???? in the console view.

Return to the main readme file