The IsBadStringPtr function verifies that the calling process has read access to a range of memory pointed to by a string pointer.
BOOL IsBadStringPtr(
LPCTSTR lpsz, // address of string
UINT ucchMax // maximum size of string
);
If the calling process has read access to all bytes up to the string's terminating null character or up to the number of bytes specified by ucchMax, the return value is zero.
If the calling process does not have read access to all bytes up to the string's terminating null character or up to the number of bytes specified by ucchMax, the return value is nonzero. To get extended error information, call GetLastError
If the application is compiled as a debugging version, and the process does not have read access to all bytes in the specified memory range, the function causes an assertion and breaks into the debugger. Leaving the debugger, the function continues as usual, and returns a nonzero value This behavior is by design, as a debugging aid.
If the calling process has read access to some, but not all, of the bytes in the specified memory range, the return value is nonzero.
In a preemptive multitasking environment, it is possible for some other thread to change the process's access to the memory being tested. Even when the function indicates that the process has read access to the specified memory, you should use structured exception handling when attempting to access the memory. Use of structured exception handling enables the system to notify the process if an access violation exception occurs, giving the process an opportunity to handle the exception.
Windows NT: Requires version 3.1 or later.
Windows: Requires Windows 95 or later.
Windows CE: Unsupported.
Header: Declared in winbase.h.
Import Library: Use kernel32.lib.
Unicode: Implemented as Unicode and ANSI versions on Windows NT.
Memory Management Overview, Memory Management Functions, IsBadCodePtr, IsBadReadPtr, IsBadWritePtr