Index
A
- Application Data Integrity (ADI)
Using the libdiscoverADI Library to Find Memory Access
Errors
B
- binaries
- instrumented with discover
- changing the runtime behavior ofSUNW_DISCOVER_OPTIONS Environment Variable
- writing to a specific fileOutput Options
- changing the runtime behavior of
- instrumented with uncover, runningRunning the Instrumented Binary
- instrumenting for discoverInstrumenting a Binary
- instrumenting for uncoverInstrumenting the Binary
- preparing for discoverSupported Binaries
- that cannot be used by discoverBinaries That Use Preloading or Auditing Are Incompatible
- instrumented with discover
- bit.rc initialization filesbit.rc Initialization Files
- telling discover not to readInstrumentation Options
- telling discover not to read
C
- custom memory allocators
D
- Discover
- requirements for usingRequirements for Using discover
- requirements for using
- discover
- Application Data Integrity (ADI)Hardware-Assisted Checking Using Silicon Secured Memory (SSM)
- doing full read-write instrumentation of librariesInstrumentation Options
- doing write-only instrumentation for executablesInstrumentation Options
- forcing reinstrumentation of cached librariesCaching Options
- hardware-assisted checkingHardware-Assisted Checking Using Silicon Secured Memory (SSM)
- allocation/free stack tracesInstrumentation Options
- configuration optionsInstrumentation Options for discover ADI Mode
- discover ADI libraryUsing the libdiscoverADI Library to Find Memory Access
Errors
- errors caughtErrors Caught by the libdiscoverADI Library
- libdiscoverADI.so
- precise ADI modeInstrumentation Options
- allocation/free stack traces
- ignoring shared libraries
- instrumenting the named binary onlyInstrumentation Options
- limitationsLimitations When Using discover
- false negativesNon-Annotated Code Might Cause False Results
- false positivesNon-Annotated Code Might Cause False Results
- false negatives
- memory access error examplesMemory Access Errors
- memory access errorsMemory Access Errors
- memory access warningsMemory Access Warnings
- options
- –i adiInstrumentation Options
- –i dataraceInstrumentation Options
- –i memcheckInstrumentation Options
- –i adi
- running in litemodeInstrumentation Options
- Silicon Secured Memory (SSM)Hardware-Assisted Checking Using Silicon Secured Memory (SSM)
- specifying cache directoryCaching Options
- specifying verbose modeOther Options
- specifying what happens if the instrumented binary forksInstrumentation Options
- writing error data to directory for use by Code AnalyzerOutput Options
- Application Data Integrity (ADI)
- discover ADI
- custom memory allocatorsCustom Memory Allocators and the discover ADI Library
- requirements and limitationsRequirements and Limitations of Using libdiscoverADI
- custom memory allocators
- discover ADI library
- errors caughtErrors Caught by the libdiscoverADI Library
- errors caught
- discover APIsdiscover APIs
- Finding leaks in a long-running programFinding Leaks in a Server or Long-Running Program
- Finding leaks in a serverFinding Leaks in a Server or Long-Running Program
- Finding memory leaks withFinding Memory Leaks With discover APIs
- Finding leaks in a long-running program
- discover reports
- ASCIIAnalyzing the ASCII Report
- error messagesASCII Warning and Error Message Descriptions
- heap blocks left allocatedASCII Memory Leak Report
- memory leaksASCII Memory Leak Report
- summaryASCII Report Summary
- unfreed heap blocksASCII Stack Trace Report
- warning messagesASCII Warning and Error Message Descriptions
- writingOutput Options
- error messages
- error messages, interpretingInterpreting discover Error Messages
- false positivesInterpreting discover Error Messages
- avoidingPartially Initialized Memory
- caused by partially initialized memoryPartially Initialized Memory
- caused by speculative loadsSpeculative Loads
- caused by uninstrumented codeUninstrumented Code
- avoiding
- HTMLAnalyzing the HTML Report
- control panelUsing the Control Panel
- controlling types of errors displayedUsing the Control Panel
- controlling types of warnings displayedUsing the Control Panel
- Errors tabUsing the Errors Tab
- Memory Leaks tabUsing the Memory Leaks Tab
- number of blocks remaining allocatedUsing the Memory Leaks Tab
- showing all stack tracesUsing the Control Panel
- showing source code
- showing source code for all functionsUsing the Control Panel
- showing stack trace
- Warnings tabUsing the Warnings Tab
- writingOutput Options
- control panel
- limiting number of memory errors reportedOutput Options
- limiting number of memory leaks reportedOutput Options
- limiting number of stack frames shown inOutput Options
- showing mangled names inOutput Options
- showing offsets inOutput Options
- ASCII
I
- instrumenting a binary
- for data race detection with discoverInstrumentation Options
- for discoverInstrumenting a Binary
- for hardware assisted checking with discoverInstrumentation Options
- for memory error checking with discoverInstrumentation Options
- for uncoverInstrumenting the Binary
- for data race detection with discover
L
- libdiscoverADI.so
- libdiscoverADI library
N
- non-annotated code
- how discover treatsInstrumenting a Binary
- sources ofInstrumenting a Binary
- how discover treats
R
- requirements
- DiscoverRequirements for Using discover
- Discover
S
- shared libraries
- caching by discoverCaching Shared Libraries
- instrumenting with discoverInstrumenting Shared Libraries
- telling discover to ignore
- caching by discover
- Silicon Secured Memory (SSM)Using the libdiscoverADI Library to Find Memory Access
Errors
- SUNW_DISCOVER_OPTIONS environment variable
U
- Uncover
- uncover
- command examplesuncover Command Examples
- coverage report, generatingGenerating and Viewing the Coverage Report
- creating the coverage data directory in a specified directoryInstrumenting the Binary
- limitationsLimitations When Using uncover
- options
- overviewCode Coverage Tool (uncover)
- requirements for usingRequirements for Using uncover
- running in verbose modeGenerating and Viewing the Coverage Report
- turning on reporting of execution counts for instructions, blocks, and functions
- turning thread-safe profiling on and offInstrumenting the Binary
- writing data to directory for use by Code AnalyzerGenerating and Viewing the Coverage Report
- writing the instrumented binary file to a specified fileInstrumenting the Binary
- command examples
- uncover ASCII coverage reportUnderstanding the ASCII Coverage Report
- uncover coverage report for Performance Analyzer
- Functions view
- Block Covered % counterBlock Covered % Counter
- Instr Covered % counterInstr Covered % Counter
- Instr Exec counterInstr Exec Counter
- Uncoverage counterUncoverage Counter
- Block Covered % counter
- Functions view
- uncover coverage report for Performance Analyzer
- Disassembly viewDisassembly View
- Functions viewFunctions View
- Inst–Freq viewInstruction Frequency View
- Source viewSource View
- Disassembly view
- uncover coverage report for Performance AnalyzerUnderstanding the Coverage Report in Performance Analyzer
- uncover coverage report for Performance Analyzer
- uncover coverage report for Performance Analyzer
- Functions view
- Function CountFunction Count
- Function Count
- Functions view
- uncover HTML coverage reportUnderstanding the HTML Coverage Report