#12110: Windows exception handler change causes segfault with API Monitor -------------------------------------+------------------------------------- Reporter: enolan | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Runtime System | Version: 8.0.1 Resolution: | Keywords: Operating System: Windows | Architecture: | Unknown/Multiple Type of failure: Runtime crash | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by enolan): It works before the commit and doesn't after. It may be fair to blame API Monitor's developer, but the exception handlers are definitely involved. Maybe API Monitor method of hooking triggers the exception handler and it's incorrectly interpreted as a segfault? You definitely know more about this than me. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12110#comment:2 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

#12110: Windows exception handler change causes segfault with API Monitor -------------------------------------+------------------------------------- Reporter: enolan | Owner: (none) Type: bug | Status: patch Priority: normal | Milestone: 8.4.1 Component: Runtime System | Version: 8.0.1 Resolution: | Keywords: Operating System: Windows | Architecture: | Unknown/Multiple Type of failure: Runtime crash | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Phab:D3911 Wiki Page: | -------------------------------------+------------------------------------- Comment (by Ben Gamari ): In [changeset:"1825cbdbdf08ed4bd6fd6794852596078953298a/ghc" 1825cbdb/ghc]: {{{ #!CommitTicketReference repository="ghc" revision="1825cbdbdf08ed4bd6fd6794852596078953298a" Switch VEH to VCH and allow disabling of SEH completely. Exception handling on Windows is unfortunately a bit complicated. But essentially the VEH Handlers we currently have are running too early. This was a problem as it ran so early it also swallowed C++ exceptions and other software exceptions which the system could have very well recovered from. So instead we use a sequence of chains to for the exception handlers to run as late as possible. You really can't get any later than this. Please read the comment in the patch for more details. I'm also providing a switch to allow people to turn off the exception handling entirely. In case it does present a problem with their code. Test Plan: ./validate Reviewers: austin, hvr, bgamari, erikd, simonmar Reviewed By: bgamari Subscribers: rwbarton, thomie GHC Trac Issues: #13911, #12110 Differential Revision: https://phabricator.haskell.org/D3911 }}} -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12110#comment:4 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

#12110: Windows exception handler change causes segfault with API Monitor -------------------------------------+------------------------------------- Reporter: enolan | Owner: (none) Type: bug | Status: closed Priority: normal | Milestone: 8.4.1 Component: Runtime System | Version: 8.0.1 Resolution: fixed | Keywords: Operating System: Windows | Architecture: | Unknown/Multiple Type of failure: Runtime crash | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Phab:D3911 Wiki Page: | -------------------------------------+------------------------------------- Changes (by bgamari): * status: patch => closed * resolution: => fixed Comment: The double-commit was to fix erroneous authorship information. Sorry for the noise. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12110#comment:6 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler