Memory Stop Details |
The Memory checks ensure APIs for virtual space manipulations are used correctly (e.g. VirtualAlloc, VirtualFree, MapViewOfFile).
Following is a list of verifier stops that may occur when running the memory checks against a solution or project on different platforms:
Error message | Stop code |
Freeing virtual memory block with invalid size or start address | 0600 |
0601 | |
0602 | |
0603 | |
0604 | |
0605 | |
0606 | |
0607 | |
0608 | |
Freeing memory block inside current thread's stack address range | 0609 |
060A | |
060B | |
Incorrect size parameter for VirtualFree (MEM_RELEASE) operation | 060C |
060D | |
060E | |
060F | |
0610 | |
Freeing heap memory block inside current thread's stack address range | 0612 |
Unmapping memory region inside current thread's stack address range | 0613 |
0614 | |
0615 | |
0616 | |
Unexpected exception raised while initializing output buffer | 0617 |
0618 | |
0619 | |
061A | |
Unexpected exception raised in threadpool callback function. | 061B |
061C | |
061D | |
061E |
Properties
There is one property for the memory tests: ExecWritePage. This property when turned on (off by default) will generate two stops.
Double click the property to edit it. Click the check box to turn the value to True, which turns on the test.