Dump memory map on mapping failure?
Currently we have some rather delicate and platform-specific heuristics to try to create mappings near where the executable image is located. Unfortunately, when this goes wrong both the user and GHC developers are left with very little information regarding why (e.g. see #19421 (closed)). We should dump a memory map that the user can include in their bug report.