D
- Discover
- requirements for using
Requirements 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
- following forkSUNW_DISCOVER_FOLLOW_FORK_MODE Environment Variable
- 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 libdiscoverADI
- libdiscoverADI.so
- precise ADI modeInstrumentation Options
- allocation/free stack traces
- ignoring shared libraries
- instrumenting the named binary onlyInstrumentation Options
- issuing a warning if an attempt is made to instrument an uninstrumentable binaryInstrumentation Options
- limitationsLimitations When Using discover
- 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 light modeInstrumentation 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 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