Debug Routines
The debug version of the C run-time library supplies many diagnostic services that make debugging programs easier and allow developers to:
Step directly into run-time functions during debugging
Resolve assertions, errors, and exceptions
Trace heap allocations and prevent memory leaks
Report debug messages to the user
To use these routines, the _DEBUG flag must be defined. All of these routines do nothing in a retail build of an application. For more information on how to use the new debug routines, see CRT Debugging Techniques.
Debug Versions of the C Run-Time Library Routines
Routine |
Use |
.NET Framework equivalent |
|---|---|---|
Evaluate an expression and generates a debug report when the result is FALSE |
||
Similar to _ASSERT, but includes the failed expression in the generated report |
||
Confirm the integrity of the memory blocks allocated on the debug heap |
||
Sets a break point. |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Generate a debug report with a user message and send the report to three possible destinations |
System::Diagnostics::Debug::Write, System::Diagnostics::Debug::Writeline, System::Diagnostics::Debug::WriteIf, System::Diagnostics::Debug::WriteLineIf |
|
Call an application-supplied function for all _CLIENT_BLOCK types on the heap |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Dump all of the memory blocks on the debug heap when a significant memory leak has occurred |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Verify that a specified memory block is located within the local heap and that it has a valid debug heap block type identifier |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Verifies that a specified pointer is in the local heap |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Verify that a specified memory range is valid for reading and writing |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Obtain the current state of the debug heap and store it in an application-supplied _CrtMemState structure |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Compare two memory states for significant differences and return the results |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Dump information about objects on the heap since a specified checkpoint was taken or from the start of program execution |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Dump the debug header information for a specified memory state in a user-readable form |
||
Returns the block type/subtype associated with a given debug heap block pointer. |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Install a client-defined allocation function by hooking it into the C run-time debug memory allocation process |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Set a breakpoint on a specified object allocation order number |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Retrieve or modify the state of the _crtDbgFlag flag to control the allocation behavior of the debug heap manager |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Install an application-defined function that is called every time a debug dump function is called to dump _CLIENT_BLOCK type memory blocks |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Identify the file or stream to be used as a destination for a specific report type by _CrtDbgReport |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Install a client-defined reporting function by hooking it into the C run-time debug reporting process |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Installs or uninstalls a client-defined reporting function by hooking it into the C run-time debug reporting process. |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Specify the general destination(s) for a specific report type generated by _CrtDbgReport |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Track the application's progress by generating a debug report by calling _CrtDbgReport with a format string and a variable number of arguments. Provides no source file and line number information. |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Similar to the _RPTn macros, but provides the source file name and line number where the report request originated |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Allocate a specified number of memory blocks on the heap with additional space for a debugging header and overwrite buffers |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Resize a specified block of memory on the heap by expanding or contracting the block |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Free a block of memory on the heap |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Create an absolute or full path name for the specified relative path name, using _malloc_dbg to allocate memory. |
||
Get the current working directory, using _malloc_dbg to allocate memory. |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Allocate a block of memory on the heap with additional space for a debugging header and overwrite buffers |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Calculate the size of a block of memory on the heap |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Reallocate a specified block of memory on the heap by moving and/or resizing the block |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
|
Duplicates a string, using _malloc_dbg to allocate memory. |
||
Generate names you can use to create temporary files, using _malloc_dbg to allocate memory. |
Not applicable. To call the standard C function, use PInvoke. For more information, see Platform Invoke Examples. |
The debug routines can be used to step through the source code for most of the other C run-time routines during the debugging process. However, Microsoft considers some technology to be proprietary and, therefore, does not provide the source code for these routines. Most of these routines belong to either the exception handling or floating-point processing groups, but a few others are included as well. The following table lists these routines.
C Run-Time Routines That Are Not Available in Source Code Form
printf, _printf_l, wprintf, _wprintf_l, printf_s, _printf_s_l, wprintf_s, _wprintf_s_l* |
||
scanf, _scanf_l, wscanf, _wscanf_l, scanf_s, _scanf_s_l, wscanf_s, _wscanf_s_l* |
||
|
* Although source code is available for most of this routine, it makes an internal call to another routine for which source code is not provided.
Some C run-time functions and C++ operators behave differently when called from a debug build of an application. (Note that a debug build of an application can be done by either defining the _DEBUG flag or by linking with a debug version of the C run-time library.) The behavioral differences usually consist of extra features or information provided by the routine to support the debugging process. The following table lists these routines.
Routines that Behave Differently in a Debug Build of an Application
C abort routine |
C++ delete operator |
C assert routine |
C++ new operator |
For more information about using the debug versions of the C++ operators in the preceding table, see Using the Debug Heap from C++.