Examining ASSERT Statements
Suppose that when you run the debug version of your MFC application, there are no problems. However, the release version of the same application crashes, returns incorrect results, and/or exhibits some other abnormal behavior.
This problem can be caused when you place important code in an ASSERT statement to verify that it performs correctly. Because ASSERT statements are commented out in a release build of an MFC program, the code does not run in a release build.
If you are using ASSERT to confirm that a function call succeeded, consider using VERIFY instead. The VERIFY macro evaluates its own arguments in both debug and release builds of the application.
Another preferred technique is to assign the function's return value to a temporary variable and then test the variable in an ASSERT statement.
Examine the following code fragment:
char *buf; ASSERT(buf = (char *) calloc( 20, sizeof(char) )); strcpy( buf, "Hello, World" ); free( buf );
This code runs perfectly in a debug version of an MFC application. If the call to
calloc( ) fails, a diagnostic message that includes the file and line number appears. However, in a retail build of an MFC application:
- the call to
calloc( )never occurs, leaving
strcpy( )copies "
Hello, World" into a random piece of memory, possibly crashing the application or hanging the system, or
free()attempts to free memory that was never allocated.
To use ASSERT correctly, the code sample should be changed to the following:
char *buf; buf = (char *) calloc( 20, sizeof(char) ); ASSERT( buf != NULL ); strcpy( buf, "Hello, World" ); free( buf );
Or, you can use VERIFY instead:
char *buf; VERIFY(buf = (char *) calloc(20, sizeof(char) )); strcpy( buf, "Hello, World" ); free( buf );