mapped_file: reading/writing mapped memory can throw (structured) exceptions? (windows)

[xurux1-mail@…]

msdn: "Reading and Writing From a File View" (​http://msdn.microsoft.com/en-us/library/aa366801(VS.85).aspx)

"Reading from or writing to a file view can cause an EXCEPTION_IN_PAGE_ERROR exception. For example, accessing a mapped file that resides on a remote server can generate an exception if the connection to the server is lost. Exceptions can also occur because of a full disk, an underlying device failure, or a memory allocation failure. When writing to a file view, exceptions can also occur because the file is shared and a different process has locked a byte range. To guard against exceptions due to input and output (I/O) errors, all attempts to access memory mapped files should be wrapped in structured exception handlers"

DWORD dwLength; try {

dwLength = *((LPDWORD) lpMapAddress);

} except(GetExceptionCode()==EXCEPTION_IN_PAGE_ERROR ?

EXCEPTION_EXECUTE_HANDLER : EXCEPTION_CONTINUE_SEARCH)

{

Failed to read from the view.

}

... so it should be mentioned in the documentation? (windows specific)

[anonymous]

interesting:

​http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6415680

java has a get method, to access bytes in a FileChannel (=mmap'ed file), which should do the checking ...