[GHC] #14825: Access violation on Windows is not propagated to the OS

GHC ghc-devs at haskell.org
Mon Feb 19 15:58:07 UTC 2018


#14825: Access violation on Windows is not propagated to the OS
-------------------------------------+-------------------------------------
           Reporter:  varosi         |             Owner:  (none)
               Type:  feature        |            Status:  new
  request                            |
           Priority:  normal         |         Milestone:
          Component:  Runtime        |           Version:  8.2.2
  System                             |
           Keywords:                 |  Operating System:  Windows
       Architecture:  x86_64         |   Type of failure:  Debugging
  (amd64)                            |  information is incorrect
          Test Case:                 |        Blocked By:
           Blocking:                 |   Related Tickets:
Differential Rev(s):                 |         Wiki Page:
-------------------------------------+-------------------------------------
 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.

-- 
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/14825>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler


More information about the ghc-tickets mailing list