JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
What's New In The Oracle Solaris Studio 12.2 Release
search filter icon
search icon

Document Information

Preface

1.  Introducing The Oracle Solaris Studio 12.2 Release

2.  Compilers

3.  Libraries

4.  Performance Analysis Tools

The Performance Analyzer

Changes to Experiment Format

Changes to Performance Analyzer Tool

New Call Tree Tab

Enhancements to the Callers-Callees Tab

New Comparing Experiments Feature

Miscellaneous Enhancements

The er_print Command

New Data Collection Features

New dbx collector Features

A Change to er_kernel

New command er_generic

Change to en_desc

The Thread Analyzer

5.  Debugging Tools

6.  The Solaris Studio IDE

7.  Other Tools

8.  Known Problems, Limitations, and Workarounds in This Release

Index

The Thread Analyzer

The Thread Analyzer now supports data race detection for code that is instrumented at either the source level or binary level. Source-level instrumentation is unchanged in this release.

To instrument a program's binary code, you need to use the discover tool, which is included in Oracle Solaris Studio and is documented in the discover(1) man page. See also Oracle Solaris Studio 12.2 Discover and Uncover User’s Guide

For instrumenting a program's binary code to detect data races, the discover tool requires the input binary to be compiled under the following conditions:

You might also be able to use the discover tool on an earlier Solaris version running on a SPARC-based system if the binary was compiled with the compiler option -xbinopt=prepare. See the cc(1), CC(1), or f95(1) man pages for information about this compiler option.

If the binary is named a.out, you can create an instrumented binary named a.out_i with the following command:

% discover -i datarace -o a.out_i a.out

See the Oracle Solaris Studio 12.2: Thread Analyzer User’s Guide or tha(1) man page for more information.