#10435: catastrophic exception-handling disablement on Windows Server 2008 R2 -------------------------------------+------------------------------------- Reporter: malcolmw | Owner: simonmar Type: bug | Status: new Priority: normal | Milestone: Component: Runtime System | Version: 7.10.1 Resolution: | Keywords: windows, Operating System: Windows | exceptions Type of failure: Runtime crash | Architecture: x86 Blocked By: | Test Case: Related Tickets: | Blocking: | Differential Revisions: -------------------------------------+------------------------------------- Comment (by Phyx-): I've only seen this Ticket today, but the exit code has been bugging me. Getting a 127 on a SEH error is odd. Building the files I was able to re-produce the error using a fresh Win 2008 R2 VM. However running the application outside of a console or using dependencywalker that 127 became clear. I was missing the proper visual c++ runtime file. Hence the 127 which is usually "missing command" or "missing file". Can you try running dependency walker to see if you have any missing dependencies? Installing the proper VCRedist solved the first problem for me and the application then threw an unhandled exception resulting in a APPLICATION_FAULT_SEHOP and another crash. but the first part of the result is written. I have issues remote debugging on the VM so I didn't look further into this. I currently get: {{{ PS E:\> .\TestExceptions.exe Called foo() with bar=0 PS E:\> }}} -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/10435#comment:8 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler