<\/p>\n\r
When Memory Validator attaches to a target program, some memory allocations may have been made already. <\/p>\n\r
<\/p>\n\r
Although those allocations are typically in the very first startup code executed as the C runtime initialises, Memory Validator won\'t know their location. <\/p>\n\r
<\/p>\n\r
This is true even when Memory Validator launches, waits for, or is linked to the target program. <\/p>\n\r
<\/p>\n\r
Where the program has been running for a while and Memory Validator is injected<\/span> into the program, then clearly a lot<\/span> of allocations could have occurred already!<\/p>\n\r <\/p>\n\r In most cases it\'s not important to know about the C runtime initialisation memory, as the C runtime will deallocate the memory when the program shuts down. <\/p>\n\r <\/p>\n\r However, if you need Memory Validator to know about this memory you can use this update function to cause the stub to send information about all C runtime memory allocations to the Memory Validator user interface. <\/p>\n\r <\/p>\n\r These allocations won\'t have a stack trace to identify where the memory was allocated, but for the _DEBUG versions of the C runtime, there may be useful filename and line information.<\/p>\n\r <\/p>\n\r <\/p>\n\r Use one of the following methods to invoke an update:<\/p>\n\r <\/p>\n\r <\/p>\n\rInvoking a CRT memory update<\/span><\/h1>\n\r
<\/span><\/h1>\n\r
Tools <\/span>menu <\/span> Update<\/span> <\/span> <\/span> shows the CRT Memory Update dialog <\/span><\/h1>\n\r