--- title: "Error Types Reported by Dr. Memory" layout: default permalink: /page_types.html ---

Dr. Memory

Error Types Reported by Dr. Memory

Each error found by Dr. Memory is listed in the `results.txt` file (see Examining the Results). The error report includes an error number, the type of error, the address and size of the memory access in question (if applicable to the error type), a timestamp and thread identifier indicating when and where the error was detected, and a callstack of the application at the point of the error. The thread identifier can be correlated with the function of a particular thread by locating the thread creation callstack in the `global.pid.log` file in the same directory as the `results.txt` file.

The `-brief` option can be used to request simpler and in some cases easier to read (i.e., more suited to novices) error reports that hide STL and CRT paths, simplify source paths for the executable by removing the path containing the executable itself, and omit absolute addresses, thread timestamps, and instruction disassembly.

The following sections describe each type of error. Leaks are described in Memory Leaks.

- Unaddressable Access
- Uninitialized Read
- Invalid Heap Argument
- Memory Leaks
- GDI Usage Errors
- Handle Leaks
- Warning