Oracle® Solaris Studio 12.4: Performance Analyzer

Exit Print View

Updated: January 2015

Recording Experiments

    You can record an experiment on a user-mode target in three different ways:

  • With the collect command

  • With dbx creating a process

  • With dbx creating an experiment from a running process

The Profile Application dialog in Performance Analyzer runs a collect experiment.

collect Experiments

When you use the collect command to record an experiment, the collect utility creates the experiment directory and sets the LD_PRELOAD environment variable to ensure that and other libcollector modules are preloaded into the target’s address space. The collect utility then sets environment variables to inform about the experiment name, and data collection options, and executes the target on top of itself. and associated modules are responsible for writing all experiment files.

dbx Experiments That Create a Process

When dbx is used to launch a process with data collection enabled, dbx also creates the experiment directory and ensures preloading of Then dbx stops the process at a breakpoint before its first instruction, and calls an initialization routine in to start the data collection.

Java experiments can not be collected by dbx, because dbx uses a Java Virtual Machine Debug Interface (JVMDI) agent for debugging. That agent can not coexist with the Java Virtual Machine Tools Interface (JVMTI) agent needed for data collection.

dbx Experiments on a Running Process

When dbx is used to start an experiment on a running process, it creates the experiment directory but cannot use the LD_PRELOAD environment variable. dbx makes an interactive function call into the target to open, and then calls the initialization routine, just as it does when creating the process. Data is written by and its modules just as in a collect experiment.

Because was not in the target address space when the process started, any data collection that depends on interposition on user-callable functions (synchronization tracing, heap tracing, MPI tracing) might not work. In general, the symbols have already been resolved to the underlying functions so the interposition can not happen. Furthermore, the following of descendant processes also depends on interposition, and does not work properly for experiments created by dbx on a running process.

If you have explicitly preloaded before starting the process with dbx or before using dbx to attach to the running process, you can collect tracing data.