• A
    Go 1.15 support (#2011) · f9c8f7f5
    Alessandro Arzilli 提交于
    * proc: start variable visibility one line after their decl line
    
    In most cases variables shouldn't be visible on their declaration line
    because they won't be initialized there.
    Function arguments are treated as an exception.
    
    This fix is only applied to programs compiled with Go 1.15 or later as
    previous versions of Go did not report the correct declaration line for
    variables captured by closures.
    
    Fixes #1134
    
    * proc: silence go vet error
    
    * Makefile: enable PIE tests on windows/Go 1.15
    
    * core: support core files for PIEs on windows
    
    * goversion: add Go 1.15 to supported versions
    
    * proc: fix function call injection for Go 1.15
    
    Go 1.15 changed the call injection protocol so that the runtime will
    execute the injected call on a different (new) goroutine.
    
    This commit changes the function call support in delve to:
    
    1. correctly track down the call injection state after the runtime
       switches to a different goroutine.
    2. correctly perform the escapeCheck when stack values can come from
       multiple goroutine stacks.
    
    * proc: miscellaneous fixed for call injection under macOS with go 1.15
    
    - create copy of SP in debugCallAXCompleteCall case because the code
      used to assume that regs doesn't change
    - fix automatic address calculation for function arguments when an
      argument has a spurious DW_OP_piece at entry
    f9c8f7f5
disasm.go 4.7 KB