This section describes changes made to various command-line performance analysis tools. For more information, see the corresponding man pages for each command-line tool.
Data collection tools include the collect command, the dbx collector command, and the er_kernel command. Each of these tools is used to profile programs to collect data and create experiments that can be read by Performance Analyzer or er_print.
The collect utility is a tool you use to profile your application as it runs to collect data and create an experiment that can be read by Performance Analyzer or er_print.
In addition to the changes common to all data collection tools, the collect utility is changed in this release as follows:
It is now possible to disable the capture of callstacks during profiling. When profiling Java on x86, disabling the capture of callstacks can reduce the risk of fatal errors related to stack unwind. For more details, see SP_COLLECTOR_NATIVE_MAX_STACKDEPTH information in collect(1).
The er_kernel command profiles the Oracle Solaris kernel and generates an experiment that you can examine in Performance Analyzer or er_print.
The er_kernel utility is changed as follows:
Kernel profiling is now supported on Oracle Solaris VMs running under OVM (xen).
For more information, see the er_kernel(1) man page.
The er_print utility generates a plain-text version of the data views presented by the Performance Analyzer. The output is displayed on the standard output window.
The er_print utility is changed in this release as follows:
Command-line editing and history is available on Oracle Solaris.
Java and Scala applications that use large jar files are now supported.
Performance Analyzer now supports code compiled with the Intel –ipo flag.
dumpgc, a utility that dumps out Java Garbage Collector Events, is available.
The –pcs option will now show a description of various error codes associated with missing Java callstacks.
For binaries compiled with GNU compilers, the PCs and Disassembly views will now identify inlined instructions and the source associated with the leaf-most inlined code.
Support for the analysis of Scala applications is now available.
For more information, see the er_print(1) man page.
The er_archive command has the following updates:
New command option –d path — This option archives to the common directory specified by the absolute path, path.
New command option –r path — This option archives to the common directory specified by the relative path, path.
The commands bw, ripc, spot, spot_cmds, spot_cmds_timing, spot_diff, and traps are no longer supported.