Visible to Intel only — GUID: GUID-9FD0F772-C260-41B3-975C-6FA212CB4C4E
Context Menus: Project Navigator
Context Menus: Sources Window Panes
Context Menus: Summary Window Panes
Dialog Box: Corresponding inspxe-cl Command Options
Dialog Box: Create a Project
Dialog Box: Create Suppression
Dialog Box: Custom Analysis
Dialog Box: Delete Suppressions
Dialog Box: Export Result
Dialog Box: Merge States
Dialog Box: Options-Debugger
Dialog Box: Options-General
Dialog Box: Options-Result Location
Dialog Box: Options-State Management
Dialog Box: Problem Report
Dialog Box: Project Properties-Binary/Symbol Search
Dialog Box: Project Properties-Source Search
Dialog Box: Project Properties-Suppressions
Dialog Box: Project Properties-Target
Dialog Box: Refine Source File Set
Dialog Box: Select Stack Frame(s)
Dialog Box: View Stack
Hot Keys
Pane: Analysis Type-Custom
Pane: Analysis Type-Memory Errors
Pane: Analysis Type-Threading Errors
Pane: Application Output
Pane: Code and Stack
Pane: Code Locations
Pane: Collection Log
Pane: Collector Messages
Pane: Compare Results
Pane: Filters
Pane: Import Result
Pane: Launch Application
Pane: Problems
Pane: Project Navigator
Pane: Timeline
Toolbar: Command
Toolbar: Intel Inspector
Toolbar: Navigation
Window: Collection Log
Window: Compare Results
Window: Import Result
Window: Sources
Window: Summary After Analysis Is Complete
Window: Summary During Analysis
Asynchronous Buffer
Cross-thread Stack Access
Data Race
Deadlock
Host Pointer Used on Device
Incorrect memcpy Call
Invalid Deallocation
C Examples/Windows* OS
C Example/Linux* OS
Possible Correction Strategies
Invalid Kernel Argument
Invalid Kernel Argument Size
Invalid Memory Access
Invalid Partial Memory Access
Lock Hierarchy Violation
Memory Growth
Memory Leak
Memory Not Deallocated
Mismatched Allocation/Deallocation
Mismatched Queue
Missing Allocation
Non-Host Pointer
Pointer from Different Device
Thread Exit Information
Thread Start Information
Unhandled Application Exception
Uninitialized Memory Access
Uninitialized Partial Memory Access
appdebug
app-working-dir
archive-name
baseline-result
collect
collect-with
command
convert-suppression-file
create-breakpoints
create-suppression-file
csv-delimiter
debug-this
executable-of-interest
export
filter
finalize
format
help
include-snippets
include-sources
import
knob
knob-list
merge-states
module-filter
module-filter-mode
no-auto-finalize
no-summary
option-file
quiet
report
report-all
report-output
result-dir
return-app-exitcode
search-dir
sort-asc
sort-desc
suppression-file
user-data-dir
verbose
version
Visible to Intel only — GUID: GUID-9FD0F772-C260-41B3-975C-6FA212CB4C4E
Invalid Deallocation
Occurs when an application calls a deallocation function with an address that does not correspond to dynamically allocated memory.
ID |
Code location |
Description |
---|---|---|
1 |
Invalid deallocation site |
Represents the location from which the invalid call to a deallocation function was made. |
C Examples/Windows* OS
int x = 1; int *p = &x; VirtualFree(p, 1, MEM_DECOMMIT);
void *p = VirtualAlloc(NULL,1,MEM_COMMIT,PAGE_READWRITE); VirtualFree(p,1,MEM_DECOMMIT); VirtualFree(p,1,MEM_DECOMMIT);
C Example/Linux* OS
void *p = mmap(NULL, 8, PROT_READ, MAP_PRIVATE | MAP_ANONYMOUS, 0, 0); munmap(p, 8); munmap(p, 8);
Possible Correction Strategies
If |
Do This |
---|---|
This code location should free memory. |
Change the code to pass in dynamically allocated memory. |
This code location does not need to free memory. |
Remove the call to the deallocation function. |
CAUTION:
Parent topic: Problem Type Reference