Try
Inside CRT: Debug Heap Management[
^]
But from my own notes also:
This is a list of some of the know magic numbers used by
Microsoft which can be useful to know when debugging an application.
0xABABABAB
Guard Bytes used by HeapAlloc() or LocalAlloc to mark "no man’s land" after allocated heap memory.
0xBAADFOOD
Used by LocalAlloc(LMEM_FIXED) to mark uninitialised allocated heap memory.
0xBEEFCACE
Used by Microsoft .NET as a magic number in resource files.
0xCCCCCCCC
Used by the C++ debugging runtime library to mark uninitialised stack memory.
(You need to compile with /GZ for this to occur - 0xCC is the opcode for INT 3 - breakpoint)
0xCDCDCDCD
Used by the C++ debugging runtime library to mark uninitialised heap (malloc/new) memory
0xDEADDEAD
A Windows STOP error code used when the user manually initiates a crash.
0xFDFDFDFD
Guard Bytes / Fence memory used by the C++ debugging heap to mark "no man’s land" before
and after allocated heap memory.
0xFEEEFEEE
Used by HeapFree() to mark freed heap memory.
0xDDDDDDDD
The freed (free/delete) blocks kept unused in the debug heap’s linked list when the
_CRTDBG_DELAY_FREE_MEM_DF flag is set are currently filled with 0xDD.