Memory debugging
This section provides troubleshooting information about memory debugging.
- The View Pointer Details window says a pointer is valid but does not show you which line of code it was allocated on
- mprotect fails error when using memory debugging with guard pages
- Allocations made before or during
MPI_Init
show up in Current Memory Usage but have no associated stack back trace - Deadlock when calling printf or malloc from a signal handler
- Program runs more slowly with Memory Debugging enabled