Access violation on Windows is not propagated to the OS
We're using Haskell in production environment. Some times we get exceptions, like this: "Access violation in generated code when reading 0000000000000000"
and nothing more. This is extremely hard and time consuming to debug where this exception came from. There is no information about at which address was the exception thrown. The correct way on Windows is such exceptions to be propagated to the operating system. This way we will attach a debugger to the process and it'll get and visualize where the exception happened. Currently GHC runtime is catching the exception, skip its source information and present that uninformative message to the user.