• Tamar Christina's avatar
    Add stack traces on crashes on Windows · 99c61e22
    Tamar Christina authored
    Summary:
    This patch adds the ability to generate stack traces on crashes for Windows.
    When running in the interpreter this attempts to use symbol information from
    the interpreter and information we know about the loaded object files to
    resolve addresses to symbols.
    
    When running compiled it doesn't have this information and then defaults
    to using symbol information from PDB files. Which for now means only
    files compiled with ICC or MSVC will show traces compiled.
    
    But I have a future patch that may address this shortcoming.
    
    Also since I don't know how to walk a pure haskell stack, I can for now
    only show the last entry. I'm hoping to figure out how Apply.cmm works to
    be able to walk the stalk and give more entries for pure haskell code.
    
    In GHCi
    
    ```
    $ echo main | inplace/bin/ghc-stage2.exe --interactive ./testsuite/tests/rts/derefnull.hs
    GHCi, version 8.3.20170830: http://www.haskell.org/ghc/  :? for help
    Ok, 1 module loaded.
    Prelude Main>
    Access violation in generated code when reading 0x0
    
     Attempting to reconstruct a stack trace...
    
       Frame        Code address
     * 0x77cde10    0xc370229 E:\..\base\dist-install\build\HSbase-4.10.0.0.o+0x190031
                     (base_ForeignziStorable_zdfStorableInt4_info+0x3f)
    ```
    
    and compiled
    
    ```
    Access violation in generated code when reading 0x0
    
     Attempting to reconstruct a stack trace...
    
       Frame        Code address
     * 0xf0dbd0     0x40bb01 E:\..\rts\derefnull.run\derefnull.exe+0xbb01
    ```
    
    Test Plan: ./validate
    
    Reviewers: austin, hvr, bgamari, erikd, simonmar
    
    Reviewed By: bgamari
    
    Subscribers: rwbarton, thomie
    
    Differential Revision: https://phabricator.haskell.org/D3913
    99c61e22
Flags.hsc 18.1 KB